Facilitating integrity of telemetry connectivity between an implantable device and a remote device

ABSTRACT

Systems, apparatus, methods and computer-readable storage media that facilitate monitoring the integrity of telemetry connectivity between an implantable device and an external device are provided. In one embodiment, an implantable device includes a monitoring component that monitors advertisement signal information identifying an amount of advertisement signals transmitted to the external device within a defined time period, and telemetry session information identifying an amount of the telemetry sessions that are established between the external device and the implantable device within the defined time period. A connectivity assessment component of the implantable device further determines whether a telemetry connectivity problem exists between the external device and the implantable device based on a degree of miscorrelation between the advertisement signal information and the telemetry session information.

TECHNICAL FIELD

This disclosure relates generally to implantable devices and, moreparticularly, to systems, apparatus, methods and computer-readablestorage media facilitating integrity of telemetry connectivity betweenan implantable device and a remote device.

BACKGROUND

Modern healthcare facilitates the ability for patients to lead healthyand full lives. Implantable medical devices (IMDs) are often utilizedfor such medical advances. For example, IMDs such as pacemakers,implantable cardioverter-defibrillators (ICDs), neurostimulators, anddrug pumps can facilitate management with a wide range of ailments,including, but not limited to, cardiac arrhythmias, diabetes, andParkinson's disease. Modern IMDs are entrusted with vital tasks such asmeasuring and collecting data about vital signs and facilitating theprovisioning of the collected data to doctors and nurses using telemetrycommunication. For example, in many applications, vital information isregularly and automatically communicated between an implantable deviceand a remote device, such as a remote device accessible to the patientwearing the implantable device and/or medical caregiver. Therefore, theintegrity of telemetry connectivity between the implantable device andthe remote device is of importance.

SUMMARY

The following presents a simplified summary of one or more of theembodiments including, but not limited to, provide a basic understandingof one or more of the embodiments. This summary is not an extensiveoverview of the embodiments described herein. It is intended to neitheridentify key or critical elements of the embodiments nor delineate anyscope of embodiments or the claims. Its sole purpose is to present someconcepts of the embodiments in a simplified form as a prelude to themore detailed description that is presented later. It will also beappreciated that the detailed description can include additional oralternative embodiments beyond those described in the Summary section.

Embodiments described herein include apparatus, methods andcomputer-readable storage media that facilitate monitoring the integrityof telemetry connectivity between an implantable device and an externaldevice. In some embodiments, the implantable device is or includes anIMD. In other embodiments, the implantable device is or includes adevice configured to interact with the IMD. In these embodiments, boththe implantable device and the IMD can be implanted within a patient.

In one embodiment, an implantable device is provided. The implantabledevice can include: a memory that stores executable components; and aprocessor coupled to the memory and configured to execute the executablecomponents stored in the memory. The executable components can include amonitoring component configured to monitor advertisement signalinformation identifying an amount of advertisement signals transmittedfrom the implantable device to the external device within a defined timeperiod, and telemetry session information identifying an amount oftelemetry sessions that are established between the external device andthe implantable device within the defined time period. In addition, theimplantable device can include a connectivity assessment componentconfigured to determine whether a telemetry connectivity problem existsbetween the external device and the implantable device based on at leastone of a number of discovery events within the defined time period or aratio corresponding to the amount of telemetry sessions that areestablished between the external device and the implantable devicewithin the defined time period relative to the amount of theadvertisement signals transmitted to the external device within thedefined time period.

In one embodiment, the connectivity assessment component is configuredto determine that the telemetry connectivity problem exists between theexternal device and the implantable device based on at least one of thenumber of discovery events being less than a threshold number or theratio being less than a threshold ratio.

The components of the implantable device can also include a notificationcomponent configured to generate a notification indicating the telemetryconnectivity problem exists between the external device and theimplantable device based on a determination that at least one of thenumber is below the threshold number or the ratio is below the thresholdratio. The notification component can also send the notification to theexternal device for rendering at the external device or for relaying, bythe external device, to another device.

In another embodiment, the implantable device can include aconfiguration component configured to receive a command instructing theimplantable device to reconfigure a telemetry communication protocolemployed by the implantable device to communicate with the externaldevice based on a determination that an amount of the advertisementsignals that are received by the external device from the implantabledevice within the defined time period is below a threshold amount.

In another embodiment, a method is provided. The method can includemonitoring, by a device including a processor, telemetry connectivityinformation including advertisement signal information identifying timesadvertisement signals are received by the device from an implantabledevice. The method can also include determining, by the device, whethera telemetry connectivity error condition exists associated withperforming telemetry communication between the device and theimplantable device based on an amount of the advertisement signalsreceived within a defined time period relative to a threshold amount.The method can also include, generating, by the device, a notificationidentifying the telemetry connectivity error condition based on adetermination that the telemetry connectivity error condition exists.

In one embodiment, the determining that the telemetry connectivity errorcondition exists is based on the amount of the advertisement signalsreceived within the defined time period being below the thresholdamount. In some embodiments, the method also includes performing atleast one of rendering, by the device, the notification at the device,or transmitting, by the device, the notification to another device,wherein the other device includes the implantable device or a serverdevice.

In one embodiment, the determining also includes determining that thetelemetry connectivity error condition exists based on a duration oftime between reception of two or more of the advertisement signals beingabove a threshold duration.

In some embodiments, the telemetry connectivity information alsoincludes telemetry session information identifying an amount oftelemetry sessions established between the device and the implantabledevice within the defined time period. The determining whether thetelemetry connectivity error condition exists can be also based on apercentage value corresponding to the amount of telemetry sessionsestablished relative to the amount of the advertisement signals receivedbeing less than a threshold percentage value.

In yet another embodiment, a system is provided. The system can includean implantable device configured to transmit advertisement signals usinga defined telemetry communication protocol. The system can also includean external device configured to perform telemetry communication withthe implantable device based on reception of the advertisement signals,and monitor advertisement signal information identifying an amount ofthe advertisement signals received by the external device within adefined period of time. The external device can further facilitatedetermining whether a telemetry connectivity error condition exists inassociation with performance of the telemetry communication with theimplantable device based on evaluation of the advertisement signalinformation with respect to the defined telemetry communicationprotocol. In various embodiments, the system can further include aserver device, wherein the external device is configured to send theadvertisement signal information to the server device and the serverdevice is configured to perform the evaluation. For example, the serverdevice can determine that the telemetry connectivity error conditionexists based on a determination that the amount of the advertisementsignals received is below a threshold amount.

In yet another embodiment, a device configured to communicate with animplantable device is provided. The device can include: a memory thatstores executable components; and a processor coupled to the memory andconfigured to execute the executable components stored in the memory.The executable components can include a communication componentconfigured to facilitate performance of telemetry communication betweenthe device and an implantable device, and a monitoring componentconfigured to monitor telemetry connectivity information includingadvertisement signal information identifying times at whichadvertisement signals, transmitted by the implantable device, arereceived by the device. The device can further include a connectivityassessment component configured to determine whether a telemetryconnectivity error condition exists associated with the performance oftelemetry communication with the implantable device based on an amountof the advertisement signals received within a defined time periodrelative to a threshold amount. The communication component canfacilitate the performance of telemetry communication between the deviceand the implantable device using a BLUETOOTH® Low Energy communicationprotocol.

In some embodiments, a notification component of the device isconfigured to generate a notification identifying the telemetryconnectivity error condition based on a determination that the telemetryconnectivity error condition exists. The communication component of thedevice can further be configured to transmit the notification to anotherdevice, such as the implantable device or a server device. In oneembodiment, the telemetry connectivity information further includetelemetry session information identifying an amount of telemetrysessions established between the device and the implantable devicewithin the defined time period. According to this implementation, theconnectivity assessment component is further configured to determinethat the telemetry connectivity error condition exists based on apercentage value representative of the amount of advertisement signalsreceived relative to the amount of the telemetry sessions establishedbeing less than a threshold percentage value.

Other embodiments and various non-limiting examples, scenarios andimplementations are described in more detail below. The followingdescription and the drawings set forth certain illustrative embodimentsof the specification. These embodiments are indicative, however, of buta few of the various ways in which the principles of the specificationcan be employed. Other advantages and novel features of the embodimentsdescribed will become apparent from the following detailed descriptionof the specification when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic diagram of an example, non-limitingmedical device telemetry system that monitors integrity of telemetryconnectivity between an implantable device and an external device inaccordance with one or more embodiments described herein.

FIG. 2 illustrates a block diagram of an example, non-limiting externaldevice for which integrity of telemetry connectivity with an implantabledevice is monitored in accordance with one or more embodiments describedherein.

FIG. 3 illustrates a block diagram of an example, non-limiting tableincluding telemetry connectivity information monitored by an externaldevice in accordance with one or more embodiments described herein.

FIG. 4 illustrates a block diagram of an example, non-limitingimplantable device for which integrity of telemetry connectivity with anexternal device is monitored in accordance with one or more embodimentsdescribed herein.

FIG. 5 illustrates a block diagram of an example, non-limiting tableincluding telemetry connectivity information monitored by an implantabledevice in accordance with one or more embodiments described herein.

FIG. 6 illustrates a block diagram of an example, non-limiting serverdevice in accordance with one or more embodiments described herein.

FIGS. 7-11 illustrate flow diagrams of example, non-limiting methods formonitoring integrity of telemetry connectivity between an implantabledevice and an external device in accordance with one or more embodimentsdescribed herein.

FIG. 12 illustrates a block diagram of an example, non-limiting computeroperable to facilitate monitoring the integrity of telemetryconnectivity between an implantable device and an external device inaccordance with one or more embodiments described herein.

DETAILED DESCRIPTION

The following detailed description is merely illustrative and is notintended to limit embodiments and/or application or uses of embodiments.Furthermore, there is no intention to be bound by any expressed orimplied information presented in the preceding Technical Field,Background or Summary sections, or in the Detailed Description section.

One or more embodiments are now described with reference to thedrawings, wherein like referenced numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth including, but notlimited to, provide a more thorough understanding of the one or moreembodiments. It is evident, however, in various cases, that the one ormore embodiments can be practiced without these specific details.

Additionally, the following description refers to components being“connected” and/or “coupled” to one another. As used herein, unlessexpressly stated otherwise, the terms “connected” and/or “coupled” meanthat one component is directly or indirectly connected to anothercomponent, mechanically, electrically, wirelessly, inductively orotherwise. Thus, although the figures can depict example arrangements ofcomponents, additional and/or intervening components can be present inone or more embodiments.

With reference now to the drawings, FIG. 1 illustrates a schematicdiagram of an example, non-limiting, medical device telemetry system 100for monitoring integrity of telemetry connectivity between animplantable device and an external device in accordance with one or moreembodiments described herein. In the embodiment shown, medical devicetelemetry system 100 includes an implantable device 104 implanted withina body 102, an external device 116, and a server device 122. While theserver device 122 is shown in FIG. 1, in some embodiments, the medicaldevice telemetry system 100 includes the implantable device 104 and theexternal device 116 but need not include the server device 122.

In some embodiments, the implantable device 104 is an IMD that is alsoconfigured to facilitate one or more diagnostic or treatment functionsrelative to the body 102. In other embodiments, the implantable device104 is separate from an IMD (not shown in this embodiment) that is alsoimplanted within the body 102 and communicatively and/or electricallycoupled to the IMD.

Embodiments of devices, apparatus and systems herein can include one ormore machine-executable components embodied within one or more machines(e.g., embodied in one or more computer-readable storage mediaassociated with one or more machines). Such components, when executed bythe one or more machines (e.g., processors, computers, computingdevices, virtual machines, etc.) can cause the one or more machines toperform the operations described.

Various embodiments of medical device telemetry system 100 are describedin connection with operations including monitoring the integrity oftelemetry connectivity between the implantable device 104 and theexternal device 116. The implantable device 104 and the external device116 are configured to use telemetry communication link 118 to exchangevarious types of information. In some embodiments, the implantabledevice 104 and the external device 116 can establish a trusted wirelesspersonal area network (PAN) via the telemetry communication link 118.After establishing the PAN, the external device 116 and the implantabledevice 104 can communicate information. For example, using the telemetrycommunication link 118, the external device 116 can read data capturedby the implantable device 104 (e.g., physiological or biometric data,such as electrogram data, performance data regarding operation of theimplantable device 104, etc.).

In another example, using the telemetry communication link 118, theexternal device 116 can send programming/configuration information tothe implantable device 104 for application by the implantable device104. The implantable device 104 can also transmit, using the telemetrycommunication link 118, information to the external device 116. Theinformation can include, but is not limited to, sensed physiologicaldata, diagnostic determinations made based on the sensed physiologicaldata, and/or performance data regarding operation of the implantabledevice 104 (e.g., remaining batter level, logged information regardingtiming of reception/transmission of signals, received signal strengthindicator (RSSI) information, throughput of received data packets,number of successfully completed telemetry sessions, etc.).

In some embodiments, the external device 116 can also provideinformation received from the implantable device 104 (and/ordeterminations or inferences made at the external device 116 based onthe information) to a server device 122 via another communication link120. For example, communication link 120 can include a telemetrycommunication link established between the external device 116 and theserver device 122 using a wide area network (WAN). By way of example,but not limitation, the server device 122 can be associated with anetworked medical monitoring service that is configured to remotelymonitor information collected by implantable devices worn by patients(e.g., implantable device 104). The server device 122 can monitor andlog the data, process the data and/or provide other users (e.g., medicalcaregiver personnel) access to the data via a telecommunication network.

In some embodiments, the server device 122 can also notify one or moreuser devices in response to reception of information that indicates atrigger event. For example, the server device 122 can notify a patientdevice (e.g., a device associated with the person wearing theimplantable device 104) and/or the caregiver device in response toreception of physiological information indicating the patient's heartelectrical activity is abnormal. In another example, the server device122 can notify a patient device and/or the caregiver device in responseto reception of information indicating telemetry connectivity betweenthe implantable device 104 and the external device 116 is or may becompromised.

The external device 116, the implantable device 104, and/or the serverdevice 122 can communicate using various wireless communicationprotocols configured to facilitate telemetry communication betweendevices over various distances. For example, the respective devices cancommunicate with one another using communication protocols including,but not limited to, a near field communication (NFC) based protocol, aBLUETOOTH® technology-based protocol (e.g., BLUETOOTH® low energy (BLE)protocol), a ZigBee® protocol, a WirelessHART® protocol, a Z-Wave® basedcommunication protocol, an advanced and adaptive network topology (ANT)based protocol, a radio frequency (RF) based communication protocol, anInternet Protocol (IP) based communication protocol (e.g. hyper texttransfer protocol (HTTP), session initiation programming (SIP), IPversion 6 over low power wireless personal area networks (6LoWPAN),etc.), a cellular communication protocol, an ultra-wideband (UWB)technology-based protocol, or other forms of communication, includingboth proprietary and non-proprietary communication protocols.

In various embodiments, communication between the respective devices ofmedical device telemetry system 100 (e.g., implantable device 104,external device 116, and server device 122) can be facilitated over apersonal area network (PAN) or a local area network (LAN) (e.g., aWireless Fidelity (Wi-Fi) network) that can provide for communicationover greater distances than the NFC or BLE protocol and can provideother advantages (e.g., stronger encryption protocols). In otherembodiments, the external device 116, the implantable device 104 and/orthe server device 122 can communicate with one another and/or anotherdevice (e.g., another server device or a second external device) over awide area network (WAN) using HTTP-based communication protocols. In oneembodiment, the external device 116 is configured to communicate withthe implantable device 104 and the server device 122 using disparatecommunication protocols and/or disparate communication networks. Forexample, the external device 116 and the implantable device 104 canestablish a PAN and communicate using BLE and the external device 116and the server device 122 can be connected via a LAN or a WAN andcommunicate using a cellular or IP based communication protocol. Inother embodiments, the respective devices of medical device telemetrysystem 100 can be configured to communicate using same or similarcommunication protocols via same or similar telecommunication networks.

The external device 116 can include a wide variety of computing devices.For example, the external device 116 can include, but is not limited to,a personal computing (PC) device, such as a smartphone, a tablet PC, anotebook, a personal digital assistant (PDA), a wearable device, oranother type of handheld computing device. In some embodiments, theexternal device 116 includes a PC that is associated with the userwearing the implantable device 104. For example, the external device 116can include a smartphone or other type of handheld or wearable devicethat is owned and operated by the patient wearing the implantable device104. In another example, the external device 116 can include a PC thatis operated by a medical caregiver of the patient, such as the patient'sphysician, nurse, at-home caregiver, mother, etc. In yet anotherexample, the external device 116 can include a dedicated and/orstationary electronic computing device designed to remain at a home ofthe patient or at an office of a physician.

In various exemplary embodiments, the external device 116 includes anoff-the-shelf device purchased at a store that can be configured toperform a variety of computing applications. These devices areconfigured to employ various types of commercially available telemetryprotocols to communicate with other devices. For example, many modernmobile devices such as smartphones, tablet personal computer (PC), andthe like are configured to communicate using public telemetry protocols,including, but not limited to, BLUETOOTH® based communication protocols(e.g., BLE), NFC, Wi-Fi, Zigbee®, RF4CE, WirelessHART, 6LoWPAN, Z-Wave,ANT, and the like. The use of such commercially available telemetryprotocols for wireless communication between implantable devices (e.g.,implantable device 104) and external devices (e.g., external device 116)more easily facilitates widespread provisioning of telemetry solutions.

Medical device telemetry system 100 provides various techniques formonitoring the integrity and quality of telemetry connectivity betweenthe implantable device 104 and the external device 116. Medical devicetelemetry system 100 also provides techniques for diagnosing telemetryconnectivity problems detected between the implantable device 104 andthe external device 116. For example, medical device telemetry system100 can identify when the telemetry communication link 118 between theexternal device 116 and the implantable device 104 fails to facilitateexchange or efficiently exchange information between the external device116 and the implantable device 104 in accordance with a definedtelemetry communication scheme employed by the respective devices.

In response to a determination that a telemetry connectivity problembetween the external device 116 and the implantable device 104 exists,medical device telemetry system 100 can also provide a notificationregarding the telemetry connectivity problem. For example, thenotification can be provided to the patient wearing the implantabledevice 104, a medical caregiver associated with the patient wearing theimplantable device, a user operating the external device 116, a systemassociated with monitoring information detected by the implantabledevice 104, etc.

The techniques employed by medical device telemetry system 100 tomonitor and evaluate the integrity and quality of wireless telemetryconnectivity between the external device 116 and the implantable device104 can be applied to various types of wireless telemetry communicationprotocols. In one or more exemplary embodiments, these techniques aretailored to monitor and evaluate the integrity and quality of wirelesstelemetry connectivity between the implantable device 104 and theexternal device 116 facilitated using commercially available (e.g., openaccess) short range wireless telemetry communication protocol, such asBLE communication protocol and the like.

In one or more embodiments, the external device 116, the implantabledevice 104, and/or the server device 122 are configured to monitortelemetry connectivity information associated with performance oftelemetry communication between the external device 116 and theimplantable device 104. For example, the external device 116 can logsignal information associated with signals received by the externaldevice 116 from the implantable device 104 and/or signals transmitted bythe external device 116 to the implantable device 104. The signalinformation can include, but is not limited to, timing of reception ofadvertisement or beacon signals transmitted by the implantable device104, occurrence of successful connection events between the externaldevice 116 and the implantable device 104, RSSI information associatedwith strengths of signals received from the implantable device 104,timing of interrogation signals sent by the external device 116 to theimplantable device 104, number of the interrogation signals to which theimplantable device 104 successfully responded, throughput of datapackets received from the implantable device 104 (e.g., downlinkthroughput), and throughput of data packets transmitted to theimplantable device 104 (e.g., uplink throughput).

Similarly, the implantable device 104 can log signal informationassociated with signals received from the external device 116 andsignals transmitted by the implantable device 104 to the external device116. For example, the implantable device 104 can log signal informationincluding, but not limited to, timing of advertisement or beacon signalssent by the implantable device 104, occurrence of successful connectionevents between the external device 116 and the implantable device 104,RSSI information associated with strengths of signals received from theexternal device 116, timing of interrogation signals received from theexternal device 116, timing of interrogation response data packets sentby the implantable device 104, throughput of data packets received fromthe external device 116, and throughput of data packet transmitted tothe external device 116.

In various embodiments, telemetry connectivity information monitored bythe external device 116 and/or the implantable device 104 can beprovided to the server device 122 for evaluation by the server device toidentify and diagnose connectivity problems between the implantabledevice 104 and the external device 116. For example, the external device116 can forward external device logged signal information to the serverdevice 122 via communication link 120. When the telemetry communicationlink 118 between the external device 116 and the implantable device 104is established and operational, the implantable device 104 can send theexternal device 116 logged implantable device signal information viatelemetry communication link 118. The external device 116 can alsoforward such information to the server device 122.

One or more of the respective devices of medical device telemetry system100 (e.g., the external device 116, the implantable device 104 and/orthe server device 122) can further process the monitored telemetryconnectivity information to determine whether a connectivity problemexists between the external device 116 and the implantable device 104.The phrase “telemetry connectivity problem” is used broadly herein torefer to the occurrence of a connectivity error condition associatedwith telemetry communication between the implantable device 104 and theexternal device 116 that is marked by an inability or hindered abilityfor the implantable device 104 to communicate with the external device116, and vice versa, according to a defined telemetry communicationscheme employed by the respective devices.

For example, a telemetry connectivity error condition can include aninability for the external device 116 and the implantable device 104 toconnect altogether (e.g., establish a telemetry communication link 118).In another example, a telemetry connectivity error condition can includean inability for the implantable device 104 and the external device 116to maintain telemetry communication link 118. In another example, atelemetry connectivity error condition can include data throughput belowa defined value or meeting a defined condition. In another example, atelemetry connectivity error condition can include inconsistent datathroughput associated with data communicated between the external device116 and the implantable device 104 after establishing the telemetrycommunication link 118. Inconsistent data throughput can include, but isnot limited to, the occurrence of throughput values varying a definedamount over a defined amount of time.

In another example, a telemetry connectivity error condition can includea decryption error or formatting error associated with data packets thatare received by the external device 116 from the implantable device 104,and vice versa. In yet another example, a telemetry connectivity errorcondition can include an inability for the external device 116 and/orthe implantable device 104 to communicate defined information betweenone another according to a defined communication schedule.

Telemetry connectivity error conditions associated with telemetrycommunication between the external device 116 and the implantable device104 can be attributed to various causes including, but not limited to,usage of incompatible telemetry communication protocol by the respectivedevices, usage of outdated telemetry communication protocols by one orboth of the devices, an error associated with configuration of thetelemetry communication protocol employed by the one or both of thedevices, a hardware malfunction associated with one or both of thedevices, interference associated with a communication channel employedby the respective devices to communicate, and/or separation of thedevices beyond the maximum distance via which the telemetrycommunication protocol employed by the devices can facilitatecommunication.

Another possible cause of telemetry connectivity issues between theexternal device 116 and the implantable device 104 could be related tothe location of the implantable device 104 within the body 102. Forexample, when the implantable device 104 is implanted within the bodyabout 4.0 or more centimeters beneath the skin, the implantable device104 is considered a “deep implant.” Some deep implants may experienceconnectivity issues with certain external devices based in part oninterference associated with internal body structures around or near thedeep implant.

Yet another possible cause of telemetry connectivity issues between theexternal device 116 and the implantable device 104 can be attributed toa telemetry shut down or time-out protocol employed by the implantabledevice 104. For example, in some implementations, the implantable device104 can be configured to temporarily deactivate telemetry to conservebattery power upon the occurrence of various triggers detected by theimplantable device 104 (e.g., reception of a threshold amount oftelemetry requests from devices that are unauthorized to communicatewith the implantable device 104). In this scenario, a detectedconnectivity issue in which the external device 116 is unable to connectwith the implantable device 104 would be intentional. Nevertheless, theexternal device 116 and the implantable device can differentiate betweenintentional and unintentional connectivity issues.

The respective devices of medical device telemetry system 100 (e.g., theexternal device 116, the implantable device 104, and the server device122) can employ various techniques to identify the occurrence oftelemetry connectivity error condition associated with performance oftelemetry communication between the external device 116 and theimplantable device 104. For example, the external device 116, theimplantable device 104 and/or the server device 122 can comparemonitored telemetry connectivity information against previouslydetermined parameters for telemetry connectivity reference informationassociated with proper telemetry connectivity and/or telemetryconnectivity reference information for improper telemetry connectivity.The results of the comparison can be employed to determine whether aconnectivity error condition exists between the implantable device 104and the external device 116.

In particular, in various embodiments, the external device 116 and theimplantable device 104 are configured to utilize a defined telemetrycommunication protocol (e.g., BLE) that instructs the external device116 and the implantable device 104 how to communicate with otherdevices. For example, the external device 116 and the implantable device104 can be configured to initially operate in a discovery mode whereinthe external device 116 and the implantable device 104 perform telemetrycommunication operations that allow the external device 116 and theimplantable device 104 to discover each other. In some embodiments,prior to communicating a defined type of information with each other(e.g., data packets that include trusted information), and/or prior tocommunicating using a defined communication radio frequency, afterdiscovery, the implantable device 104 and the external device 116 can beconfigured to perform an authentication process wherein the respectivedevices determine whether they are authorized to establish a securetelemetry connectivity link (e.g., telemetry communication link 118)with one another. In some implementations, the implantable device 104and the external device 116 can be configured to pair with one anotherin association with performing the authentication process. For example,the implantable device 104 and the external device 116 can form atrusted relationship wherein the implantable device 104 can communicatewith the external device 116, and vice versa, after discovery,authentication and pairing is established, without performing additionaldiscovery and authentication processes. After the implantable device 104and the external device 116 discover each other, pair, and/or performauthentication, they can continue to communicate with each otheraccording to the defined communication protocol.

The parameters of the defined communication protocol can be agreed uponbetween the devices in association with discovery, pairing and/orauthentication and/or can be configured or stored in memory of therespective devices. The parameters of the communication protocol canalso vary depending on the one or more applications being executed bythe respective devices. For example, the parameters of the communicationprotocol can define what type of data the respective devices are tocommunicate with one another and how the data should be formatted. Theparameters of the communication protocol can also define how the devicesare to communicate different types of data with one another (e.g., usingone-way communications or two-way communications, duration betweencommunication signals, number of data packets transmitted, receiver andtransmitter activation and deactivation periods, etc.), and when thedevices are to communicate different types data with one another. Theparameters of the communication protocol can also define one or moredesired RSSI values for signals communicated between the respectivedevices, and one or more desired throughput values for data packetscommunicated between the respective devices.

In various embodiments, the external device 116, the implantable device104, and/or the server device 122 can evaluate monitored telemetryconnectivity information (e.g., signal information logged by theexternal device 116 and/or the implantable device 104) based on thedefined communication protocol parameters to determine whether atelemetry connectivity error condition exists between the implantabledevice 104 and the external device 116. For example, the external device116, the implantable device 104, and/or the server device 122 cancompare the logged signal information regarding timing of receipt ofcertain signals, timing of transmission of certain signals, RSSI valuesassociated with received signals, throughput of received data packets,etc. with reference signal information for the defined communicationprotocol parameters that identify when the certain signals should bereceived and/or transmitted, what RSSI levels should be associated withthe received signals and what throughput values should be associatedwith received data packets. Based on the comparison, the external device116, the implantable device 104 and/or the server device 122 candetermine whether and to what degree aspects of the logged signalinformation deviates or agrees with the defined communication protocol.For example, the respective devices can determine that a telemetryconnectivity error condition associated with performance of telemetrycommunication between the implantable device 104 and the external device116 exists based on a determination that one or more aspects of thelogged signal information deviates (e.g., with respect to a thresholdvalue or threshold range) from the defined communication protocolparameters.

In some embodiments, the external device 116 and the implantable device104 can further diagnose a cause of an identified telemetry connectivityerror condition and/or determine one or more steps to correct the errorcondition based on evaluation of the monitored telemetry connectivityinformation. For example, the external device 116 and the implantabledevice 104 can determine whether the telemetry connectivity errorcondition is associated with a particular hardware failure, a particularconfiguration problem, or channel interference.

In one embodiment, the implantable device 104 is configured to evaluatethe integrity and/or performance quality of telemetry communicationbetween the external device 116 and the implantable device 104 based onreception, by the external device 116, of advertisement signalstransmitted by the implantable device 104. As used herein, advertisementsignals can also include beacon signals. Reception of an advertisementsignal by the external device 116 from the implantable device 104 isreferred to herein as a discovery event.

For example, in accordance with various short range communicationprotocols that can be employed for telemetry communication between twodevices (e.g., BLE communication protocol), a second device can beconfigured to conduct a telemetry communication session with a firstdevice after receiving an advertisement signal from the first device.

In accordance with this embodiment, the implantable device 104 isconfigured to transmit advertisement signals to facilitate establishinga telemetry communication session with the external device 116. Forexample, the advertisement signals can indicate the implantable device104 is ready and available to communicate with the external device 116.The external device 116 is configured to establish a telemetrycommunication session with the implantable device 104 based on receptionof an advertisement signal. The number, frequency and/or timing ofadvertisement signals to be transmitted by the implantable device 104can be defined based on the defined telemetry communication protocolemployed by implantable device 104 and the external device 116. Forexample, the implantable device 104 can be configured to transmit N(e.g., 480) advertisement signals within an X hour period (e.g., 24 hourperiod). In some embodiments, one advertisement signal can betransmitted approximately every three minutes. In another example, theimplantable device 104 can be configured to transmit advertisementsignals at a frequency of M (e.g., 20) advertisement signals every Yminutes (e.g., 60 minutes). In another example, the implantable device104 can be configured to transmit one advertisement signal every Kseconds (e.g., 60 seconds).

In other embodiments, the implantable device 104 can transmitadvertisement signals according to a defined schedule or based onoccurrence of trigger events. For example, the implantable device 104can transmit M signals at a K frequency between the hours of 10 am and 6pm and transmit N signals at an L frequency between the hours of 6 pmand 10 am. In another example, the implantable device 104 can transmitadvertisement signals at an increased frequency based on detection ofinformation by the implantable device 104 (e.g., biometric information)indicative of a trigger event (e.g., the biometric information isoutside a specified range). It should be appreciated that numericalvalues for the communication parameters represented by variables N, X,M, Y, K, L, etc. can change from time to time.

According to this embodiment, the external device 116 can monitor or logadvertisement signal information identifying reception of advertisementsignals from the implantable device 104. For example, the externaldevice 116 can monitor or log information identifying a number ofadvertisement signals received over a defined period of time (e.g., 24hours). The external device 116 can also time-stamp one or more (or, insome embodiments, each) advertisement signals received. The externaldevice 116 can thus track a frequency of received advertisement signalsover a defined time period or window of time and monitor durationbetween received advertisement signals. The external device 116 can beconfigured to perform such monitoring or tracking of advertisementsignal information on a continual basis. For example, the externaldevice 116 can be configured to log advertisement signal information forconsecutive periods of time (e.g., every day) or according to a definedschedule (e.g., every other day).

In one embodiment, the external device 116 is further configured toevaluate the logged advertisement signal information to identifytelemetry connectivity error conditions associated with performance oftelemetry communication between the implantable device 104 and theexternal device 116. In addition, or as an alternative, to performingthe evaluation, the external device 116 can forward the loggedadvertisement signal information to the implantable device 104 and/orthe server device 122 for evaluation. The external device 116, theimplantable device 104 and/or the server device 122 can evaluate thelogged advertisement signal information based on defined telemetrycommunication protocol parameters (e.g., defined in memory of therespective devices or otherwise accessible to the respective devices,for example, over a network) that relate an amount, a timing and/or afrequency of advertisement signals received by the external device toone or more telemetry connectivity error conditions.

For example, the respective devices can determine that a connectivityerror condition associated with performance of telemetry communicationbetween the implantable device 104 and the external device 116 existsbased on a number of received advertisement signals within a definedperiod of time being below a threshold number.

In another example, the respective devices can identify the occurrenceof a telemetry connectivity error condition associated with performanceof telemetry communication between the implantable device 104 and theexternal device 116 based on a number of received advertisement signalswithin the defined period of time being above a particular thresholdnumber. In another example, the respective devices can identify theoccurrence of a telemetry connectivity error condition associated withperformance of telemetry communication between the implantable device104 and the external device 116 based on a frequency of receivedadvertisement signals within the defined window of time being above orbelow a threshold frequency value or range.

In another example, the respective devices can identify the occurrenceof a telemetry connectivity error condition associated with performanceof telemetry communication between the implantable device 104 and theexternal device 116 based on a duration between received advertisementsignals being above or below a defined threshold duration. Still inanother example, the respective devices can identify the occurrence of atelemetry connectivity error condition associated with performance oftelemetry communication between the implantable device 104 and theexternal device 116 based on reception of advertisement signals notaccording to a defined schedule or not in accordance with a specificoperation mode associated with occurrence of a trigger event (e.g., thefrequency of advertisement signals received did not increase followingreception of information from the implantable device identifying thetrigger event).

In response to a determination that a telemetry connectivity problembetween the external device 116 and the implantable device 104 exists,the respective devices of medical device telemetry system 100 (e.g., theexternal device 116, the implantable device 104 and/or the server device122) can further provide a notification (e.g., to the patient wearingthe implantable device 104, to a user operating the external device 116,to a medical caregiver, to a system responsible for monitoringinformation, etc.) regarding the telemetry connectivity error condition.For example, in one embodiment, in response to a determination made bythe external device 116 that a telemetry connectivity error conditionassociated with telemetry communication between the external device 116and the implantable device 104 exists, the external device 116 cangenerate and render a notification at the external device 116. Forexample, the notification can include a visual notification, such as aflashing light activated at the external device 116, and/or text orimage data displayed at the external device 116 (e.g., via a displayscreen) that identifies the telemetry connectivity problem. In anotherexample, the notification can include an audible alarm.

In another implementation, in response to a determination made by theexternal device 116 that a telemetry connectivity problem exists betweenthe external device 116 and the implantable device, the external device116 can generate a notification regarding the connectivity problem andsend the notification to another device, such as the server device 122and/or send the notification to another device (not shown) associatedwith a physician, caregiver, family member and/or friend of the patientwearing the implantable device 104.

In another implementation, in response to a determination made by theserver device 122 that a telemetry connectivity problem between theexternal device 116 and the implantable device 104 exists, the serverdevice 122 can generate a notification regarding the connectivityproblem and send the notification to the external device 116 forrendering at the external device 116. In other implementations, theserver device 122 can send the notification to another device (notshown) associated with a physician, caregiver, family member and/orfriend of the patient wearing the implantable device 104. In yet anotherimplementation, in response to a determination made by the implantabledevice 104 that a connectivity problem exists, the implantable device104 can generate and send a notification to the external device 116 forrendering at the external device 116 and/or for forwarding, by theexternal device 116, to the server device 122 and/or another device (notshown) associated with a physician, caregiver, family member and/orfriend of the patient wearing the implantable device 104. Additionalaspects and embodiments of the subject telemetry connectivity integritymonitoring and evaluation techniques are discussed infra with respect toFIGS. 2-11.

It is to be appreciated that the implantable device 104 and the externaldevice 116 can include one or more devices, transducers and/or circuitsthat can facilitate telemetry communication and telemetry integritycommunication monitoring and evaluation. For example, the implantabledevice 104 and the external device 116 can respectively include atransmitter or transceiver that transforms electrical power into asignal associated with transmitted data packets. Additionally, theimplantable device 104 and the external device 116 can include one ormore devices, transducers, receivers and/or circuits that can facilitatereceiving information from one or more devices. For example, theimplantable device 104 and the external device can respectively includea receiver that transforms a signal into electrical power.

In the example shown in medical device telemetry system 100, a personoperating the external device 116 is a patient in which the implantabledevice 104 is implanted. In another example, another person (e.g., suchas medical caregiver) interacting with the patient in which theimplantable device 104 is implanted can operate the external device 116outside the body 102 in which the implantable device 104 is located. Invarious embodiments, the implantable device 104 can include any numberof different types of implantable devices configured to communicate withthe external device 116 or another external device. The particular,size, shape, placement and/or function of the implantable device 104 isnot critical to the subject disclosure in some embodiments.

In one embodiment, as mentioned, the implantable device 104 is orincludes an IMD. For example, some example IMDs can include, but are notlimited to, cardiac pacemakers, cardiac defibrillators, cardiacre-synchronization devices, cardiac monitoring devices, cardiac pressuremonitoring devices, spinal stimulation devices, neural stimulationdevices, gastric stimulation devices, diabetes pumps, drug deliverydevices, and/or any other medical devices. In various embodiments,however, the implantable device 104 can be or include any number ofother types of implantable devices that are not IMDs.

For exemplary purposes, the implantable device 104 is illustrated inmedical device telemetry system 100 as an IMD implanted within the chestof a patient and configured to provide medical treatment associated witha heart disease or condition (e.g., an implantablecardioverter-defibrillator (ICD) and/or a pacemaker). In addition to themedical treatment, the implantable device 104 can also be configured toprovide the data packetizing and communication operations describedherein. The implantable device 104 includes a housing 106 within whichelectrical components and one or more power sources are housed. Theelectrical components can be powered via the one or more power sources.A power source (not shown) can include, but is not limited to, abattery, a capacitor, a charge pump, a mechanically derived power source(e.g., microelectromechanical systems (MEMs) device), or an inductioncomponent. The various embodiments described herein can provide improvedmanagement of power associated with the one or more power sources.

The electrical components can vary depending on the particular featuresand functionality of the implantable device 104. In various embodiments,these electrical component can include, but are not limited to, one ormore processors, memories, transmitters, receivers, transceivers,sensors, sensing circuitry, therapy circuitry, antennas and othercomponents. In an embodiment, the electrical components can be formed onor within a substrate that is placed inside the housing 106. The housing106 can be formed from conductive materials, non-conductive materials ora combination thereof. For example, housing 106 can include a conductivematerial, such as metal or metal alloy, a non-conductive material suchas glass, plastic, ceramic, etc., or a combination of conductive andnon-conductive materials. In some embodiments, the housing 106 can be abiocompatible housing (e.g., a liquid crystal polymer, etc.).

In the embodiment shown, the implantable device 104 is also an IMD andfurther includes leads 110 a,b connected to the housing 106. The leads110 a,b extend into the heart and respectively include one or moreelectrodes. For example, as depicted in medical device telemetry system100, leads 110 a,b each include a respective tip electrodes 112 a,b andring electrodes 114 a,b located near a distal end of their respectiveleads 110 a,b. When implanted, tip electrodes 112 a,b and/or ringelectrodes 114 a,b are placed relative to or in a selected tissue,muscle, nerve or other location within the body 102 of the patient. Asdepicted in medical device telemetry system 100, tip electrodes 112 a,bare extendable helically shaped electrodes to facilitate fixation of thedistal end of leads 110 a,b to the target location within the body 102of the patient. In this manner, tip electrodes 112 a,b are formed todefine a fixation mechanism. In other embodiments, one or both of tipelectrodes 112 a,b can be formed to define fixation mechanisms of otherstructures. In other instances, leads 110 a,b can include a fixationmechanism separate from tip electrodes 112 a,b. Fixation mechanisms canbe any appropriate type, including a grapple mechanism, a helical orscrew mechanism, a drug-coated connection mechanism in which the drugserves to reduce infection and/or swelling of the tissue, or otherattachment mechanism.

Leads 110 a,b are connected at a proximal end of the implantable device104 via connector block 108. Connector block 108 can include one or morereceptacles that interconnect with one or more connector terminalslocated on the proximal end of leads 110 a,b. Leads 110 a,b areultimately electrically connected to one or more of the electricalcomponents within housing 106. One or more conductors (not shown) extendwithin leads 110 a,b from connector block 108 along the length of thelead to engage the ring electrodes 114 a,b and tip electrodes 112 a,b,respectively. In this manner, each of tip electrodes 112 a,b and ringelectrodes 114 a,b is electrically coupled to a respective conductorwithin its associated lead bodies. For example, a first electricalconductor can extend along the length of the body of lead 110 a fromconnector block 108 and electrically couple to tip electrode 112 a and asecond electrical conductor can extend along the length of the body oflead 110 a from connector block 108 and electrically couple to ringelectrode 114 a. The respective conductors can electrically couple tocircuitry, such as therapy circuitry or sensing circuitry, of theimplantable device 104 via connections in connector block 108.

In one or more embodiments, the implantable device 104 is configured todeliver therapy to the heart (or other location) via the electricalconductors to one or more of electrodes 112 a and 112 b and 114 a and114 b. In the case of pacing therapy, for example, therapy circuitrywithin the implantable device 104 can generate and deliver pacing pulsesvia a unipolar electrode configuration, e.g., using electrodes 112 a and112 b and a housing electrode of the implantable device 104. In otherinstances, the therapy circuitry within the implantable device 104 candeliver pacing pulses via a bipolar electrode configuration, e.g., usingelectrodes 112 a and 112 b and ring electrodes 114 a and 114 b. Thetherapy circuitry may include one or more pulse generators, capacitors,and/or other components capable of generating and/or storing energy todeliver as pacing therapy in accordance with a pacing regime storedwithin memory. Implantable device 104 can also receive sensed electricalsignals on the electrical conductors from one or more of electrodes 112a and 112 b and 114 a and 114 b. The implantable device 104 can sensethe electrical signals using either a unipolar or bipolar electrodeconfiguration. Sensing circuitry of the implantable device 104 mayprocess the sensed electrical signals and the implantable device 104 mayanalyze the processed and/or or sensed electrical signals and providethe pacing as a function of the sensed electrical signal. The sensingcircuitry may include one or more sense amplifiers, filters, rectifiers,threshold detectors, comparators, analog-to-digital converters (ADCs),or other analog or digital components.

The configuration, features and functionality of implantable device 104are merely provided as an example. In other examples, the implantabledevice 104 can include more or fewer leads extending from the housing106. For example, the implantable device 104 can be coupled to threeleads, e.g., a third lead implanted within a left ventricle of the heartof the patient. In another example, the implantable device 104 can becoupled to a single lead that is implanted within the ventricle of theheart of the patient. In other embodiments, the lead can be anextravascular lead with the electrodes implanted subcutaneously abovethe ribcage/sternum or substernally underneath or below the sternum.Example extravascular ICDs having subcutaneous electrodes are describedin U.S. Patent Publication No. 2014/0214104 (now U.S. Pat. No.9,072,914) (Greenhut et al.) and U.S. Patent Publication No.2015/0133951 (Seifert et al.), each of which is incorporated herein inits entirety. One example extravascular ICD having substernal electrodesis described in U.S. Patent Publication No. 2014/0330327(Thompson-Nauman et al.). In some embodiments, the implantable device104 can include other leads (e.g., atrial lead and/or left ventricularlead). As such, implantable device 104 can be used for single chamber ormulti-chamber cardiac rhythm management therapy. In addition to more orfewer leads, each of the leads may include more or fewer electrodes. Ininstances in which the implantable device 104 is used for therapy otherthan pacing, (e.g., defibrillation or cardioversion), the leads caninclude elongated electrodes, which may, in some instances take the formof a coil. The therapy circuitry of the implantable device 104 cangenerate and deliver defibrillation or cardioversion shocks to the heartvia any combination of the elongated electrodes and housing electrode.The therapy circuitry may include one or more high voltage (HV) outputcapacitors and a HV charging circuit, which may include one or morecapacitors, resistors, inductors, transformers, switches, or otheranalog or digital components, and discharging circuitry to delivercardioversion or defibrillation therapy, including, for example, anH-bridge circuit. In another embodiment, the implantable device 104 caninclude leads with a plurality of ring electrodes, (e.g., as used insome implantable neurostimulators), without a tip electrode or with oneof the ring electrodes functioning as the “tip electrode.”

In another embodiment, the implantable device 104 can include no leads,as in the case of an intracardiac pacemaker or a leadless pressuresensor. In the case of an intracardiac pacemaker, the device can includea housing sized to fit wholly within the patient's heart. In oneexample, the housing can have a volume that is less than 1.5 cc and,more preferably, less than 1.0 cubic centimeter (cc). However, thehousing can be greater than or equal to 1.5 cc in other examples. Theintracardiac pacemaker includes at least two electrodes spaced apartalong the outer portion of the housing for sensing cardiac electrogramsignals and/or delivering pacing pulses. Example intracardiac pacemakersare described in commonly-assigned U.S. Patent Publication No.2012/0172690 (Anderson et al.), U.S. Patent Publication No. 2012/0172941(now U.S. Pat. No. 8,386,051) (Kenneth), and U.S. Patent Publication No.2014/0214104 (now U.S. Pat. No. 9,072,914) (Greenhut et al.), each ofwhich is incorporated herein in its entirety. In the case of a leadlesspressure sensor, the device can include a housing having a fixationmember and a pressure sensing component. One example of a leadlesspressure sensor is described in U.S. Patent Publication No. 2012/0108922(now U.S. Pat. No. 8,475,372) (Schell et al.), which is incorporatedherein in its entirety.

Referring now to FIG. 2, illustrated is a block diagram of an example,non-limiting, external device 116 in accordance with one or moreembodiments described herein. The external device 116 includes anexternal device (ED) communication component 202, an ED connectivitymonitoring component 204, an ED connectivity assessment component 206,an ED notification component 208, an ED reporting component 210, and anED configuration component 212.

One or more of the components of external device 116 constitutemachine-executable component(s) embodied within machine(s), e.g.,embodied in one or more computer readable mediums (or media) associatedwith one or more machines. Such component(s), when executed by the oneor more machines, e.g., computer(s), computing device(s), virtualmachine(s), etc. can cause the machine(s) to perform the operationsdescribed. The external device 116 can include ED memory 214 for storingthe computer executable components and instructions, and ED processor216 to facilitate operation of the computer executable components andinstructions by external device 116. The external device 116 can includean ED bus 218 that couples the various components of the external device116, including, but not limited to, the ED communication component 202,the ED connectivity monitoring component 204, the ED connectivityassessment component 206, the ED notification component 208, the EDreporting component 210, the ED configuration component 212, the EDprocessor 216 and/or the ED memory 214. Repetitive description of likeelements employed in other embodiments described herein is omitted forsake of brevity.

With reference to FIGS. 1 and 2, the external device 116 can include anysuitable computing device configured to communicate with the implantabledevice 104, and in some implementations, the implantable device 104 andthe server device 122. For example, the external device 116 can include,but is not limited to, a handheld computing device, a mobile phone, asmart phone, a tablet PC, a laptop computer, a desktop computer, apersonal digital assistant (PDA) and/or a wearable device. In someembodiments, the external device 116 can include a display that canpresent information associated with the implantable device 104. Inanother embodiment, the external device 116 can include an applicationand/or a program associated with the implantable device 104.

The ED communication component 202 is configured to facilitate telemetrycommunication between external device 116 and the implantable device104. For example, the ED communication component 202 can include or bevarious hardware and software devices associated with establishingand/or conducting a telemetry communication between the external device116 and implantable device 104. For example, ED communication component202 can control operation of a transmitter-receiver or transceiver (notshown) of the external device 116 to establish a telemetry session withthe implantable device 104 and to control transmission and reception ofsignals or data packets between the external device 116 and theimplantable device 104.

The ED communication component 202 can facilitate telemetrycommunication between the external device 116 and the implantable device104 using a variety of telemetry communication protocols. For example,the ED communication component 202 can communicate with the implantabledevice 104 using communication protocols including, but not limited to,a NFC based protocol, a BLUETOOTH® technology-based protocol, a ZigBee®based protocol, a WirelessHART® based protocol, a Z-Wave® basedprotocol, an ANT based protocol, an RF based communication protocol, anIP based communication protocol, a cellular communication protocol, aUWB technology-based protocol, or other forms of communication includingboth proprietary and non-proprietary communication protocols.

In various embodiments, with reference to FIGS. 1 and 2, the EDcommunication component 202 is configured to control transmission andreception of information between the external device 116 and theimplantable device 104 via a telemetry communication link (e.g.,telemetry communication link 118) facilitated by a communicationprotocol utilizing lower energy consumption than a conventionalcommunication protocol for wirelessly transmitting data. In anon-limiting example, the ED communication component 202 controlstransmission and reception of data packets between the external device116 and the implantable device 104 using BLE protocol. While the exampleprovided describes communication according to the BLE protocol, othercommunication protocols can be employed.

In some embodiments, the ED communication component 202 is alsoconfigured to facilitate communication between the external device 116and other devices, such as server device 122. For example, the EDcommunication component 202 can employ a same or similar telemetrycommunication protocol used to communicate with implantable device 104to communicate with server device 122. In another implementation, the EDcommunication component 202 can employ a different communicationprotocol to communicate with the server device 122 relative to that usedto communicate with the implantable device 104. For example, the EDcommunication component 202 can communicate with the implantable device104 using a short-range wireless telemetry communication protocol (e.g.,BLE and the like), and with the server device 122 using a wide-rangewireless telemetry communication protocol (e.g., an IP or cellular basedcommunication protocol). Still in other embodiments, the EDcommunication component 202 can communicate with the server device 122via a wired connection.

ED connectivity monitoring component 204 is configured to monitorinformation associated with the integrity and quality of telemetryconnectivity between the external device 116 and the implantable device104, referred to herein as telemetry connectivity information. Forexample, after establishing an initial connection with the implantabledevice 104, pairing with the implantable device 104, or otherwiseestablishing an authorized telemetry communication link (e.g., atelemetry communication link 118) with the implantable device 104, theED connectivity monitoring component 204 can monitor telemetryconnectivity information over the course of operation of the implantabledevice 104. In another example, the ED connectivity monitoring component204 can monitor telemetry connectivity information according to atemporal cycle or schedule. In yet another example, the ED connectivitymonitoring component 204 can randomly monitor telemetry connectivityinformation. Still in yet another example, the ED connectivitymonitoring component 204 can monitor telemetry connectivity informationin response to a request command provided by the external device 116(e.g., a request command based on user input at the external device 116or a request command issued by the server device 122 and transmitted tothe external device via communication link 120). According to thisexample, the request can be associated with a request to perform anassessment on the quality and integrity of telemetry connectivitybetween the implantable device 104 and the external device 116. Therequest can define a type of telemetry connectivity information for theexternal device 116 to monitor and period of time over which to monitorthe telemetry connectivity information. The telemetry connectivityinformation monitored by the ED connectivity monitoring component 204can be used by the external device 116, the implantable device 104and/or the server device 122 to determine whether a telemetryconnectivity error condition exists in association performing telemetrycommunication between the external device 116 and the implantabledevice.

In one embodiment, the external device 116 can log or store thetelemetry connectivity information in ED memory 214. The ED connectivitymonitoring component 204 can remove all or portions of the loggedtelemetry connectivity information over time for replacement with newtelemetry connectivity information. In another implementation, inaddition or in the alternative to storing the telemetry connectivityinformation, the external device 116 can send the monitored telemetryconnectivity information to the implantable device 104 and/or the serverdevice 122 via ED reporting component 210 and/or ED communicationcomponent 202. For example, the ED reporting component 210 and/or the EDcommunication component 202 can send monitored telemetry connectivityinformation to the server device 122 in real-time or substantiallyreal-time as the telemetry connectivity information is monitored. Asused herein, the term “real-time” means within a defined number ofnanoseconds or milliseconds. According to this implementation, the EDreporting component 210 can send the monitored telemetry connectivityinformation to the server device 122 for processing at the server device122 to determine whether the implantable device 104 and the externaldevice 116 are experiencing a telemetry connectivity problem (e.g., viaserver device (SD) connectivity assessment component 606, as discussedinfra with respect to FIG. 6).

In another example, the ED reporting component 210 can cache monitoredtelemetry connectivity information monitored over a defined period oftime and send the monitored telemetry connectivity information in thecache to the server device 122 and/or the implantable device 104 afterpassage of the defined period of time.

In one exemplary embodiment, the ED connectivity monitoring component204 can monitor telemetry connectivity information associated withreception of advertisement signals from the implantable device 104,referred to herein as “advertisement signal information.” For example,the implantable device 104 transmits an advertisement signal includinginformation identifying the implantable device 104 and/or indicating theimplantable device 104 is available and ready for performing telemetrycommunication. In certain implementations, the advertisement signal canbe detected by various other devices within transmission range of theimplantable device 104 that are also configured to employ the same orsimilar telemetry communication protocol as the external device 116. Inother embodiments, the advertisement signals transmitted by theimplantable device 104 can be configured for reception by only theexternal device 116.

In some implementations, based on reception of an advertisement signalfrom the implantable device 104, the external device 116 is configuredto perform one or more processes that facilitate establishing atelemetry session with the implantable device 104. For example, theexternal device 116 can send a response to the implantable device 104that informs the implantable device 104 that the external device 116detected the advertisement signal and that the external device 116 wouldlike to establish a telemetry communication session with the implantabledevice 104. After transmission of an advertisement signal, theimplantable device 104 can activate the receiver for the implantabledevice 104 for a defined window of time during which the implantabledevice 104 can receive the response to the advertisement signal,transmitted by the external device 116. Based on reception of a responseto the advertisement signal from the external device 116 (and in someimplementations after performance of a pairing/authenticationprocedure), the implantable device 104 and the external device 116 canestablish a telemetry communication session.

In one embodiment, the implantable device 104 is configured to regularlytransmit advertisement signals. The number and frequency of theadvertisement signals can be fixed and/or can change from time to time.For example, the implantable device 104 can transmit N advertisementsignals within M hours. In another example, the implantable device 104can transmit one advertisement signal every X seconds or minutes. Inanother implementation, the implantable device 104 can transmitadvertisement signals according to a defined schedule or operation mode.For example, the implantable device 104 can transmit advertisementsignals at certain defined points throughout a time period (e.g., a 24hour time period). In another example, the number and frequency ofadvertisement signals to be transmitted by the implantable device 104can be based on a particular operation mode of the implantable device104, wherein the implantable device 104 is configured to operate indifferent operation modes according to a defined time schedule or basedon a trigger event (e.g., detection of biometric information outside adefined range).

In some implementations the implantable device 104 is configured totransmit two types of advertisement signals to the external device 116.The first type includes an advertisement signal referred to as an“alert,” and the second type is referred to as a “non-alert.” Theimplantable device 104 can include information with the respectiveadvertisement signals (e.g., a universal unique identifier (UUID)) thatidentifies the respective signals as either an alert or a non-alert. Insome embodiments, the alert and non-alert advertisement signals can beindicative of one or more states of the implantable device 104. Theexternal device 116 is configured to listen for one or more types ofadvertisement signals. Upon detection/reception of an advertisementsignal that indicates a desire for a telemetry session by theimplantable device 104, the external device 116 is configured to connect(or attempt to connect) with the implantable device 104, and uponconnection, send the implantable device 104 an interrogation requestmessage. The interrogation request message facilitates readinginformation from the implantable device 104 (e.g., stored in memory ofthe implantable device 104). For example, the interrogation requestmessage can request that the implantable device 104 send the externaldevice 116 certain information. Upon reception of an interrogationrequest message, the implantable device 104 is configured to respond byproviding the external device 116 with the requested information. Theexternal device 116 can be configured to process the informationreceived from the implantable device 104 and/or forward the informationto the server device 122.

A non-alert advertisement signal can facilitate provisioning ofinformation (e.g., configuration information), by the external device116 to the implantable device 104. For, example, uponreception/detection of a non-alert advertisement signal, the externaldevice 116 can connect (or attempt to connect) with the implantabledevice 104 if the external device 116 has information to send to theimplantable device 104. After a connection is established, the externaldevice 116 can send the implantable device 104 the information.

In various implementations, the server device 122 provides the externaldevice 116 with the information for provision to the implantable device104. In most scenarios, reception of a non-alert advertisement signal bythe external device 116 does not prompt the external device 116 toconnect with the implantable device 104. For example, upon reception ofa non-alert advertisement signal, the external device 116 can determinewhether the server device 122 has a pending downlink for provision, bythe external device 116, to the implantable device 104. In response to adetermination that the server device 122 does not have a pendingdownlink, the external device 116 can ignore the non-alert advertisementsignal. However, in response to a determination that the server device122 does have a pending downlink, the external device 116 can receivethe downlink from the server device 122 and respond to the non-alertadvertisement signal by establishing a connection with the implantabledevice 104 and sending the downlink to the implantable device 104.

It should be appreciated that telemetry communication protocolparameters regarding number, frequency, type and/or timing oftransmission of advertisement signals by the implantable device 104 canvary depending on the application and configuration of the implantabledevice 104. Similarly the communication protocol parameter valuesrepresented herein by variables (e.g., N, M and X) can vary depending onthe application and configuration of the implantable device 104.However, the specific telemetry communication parameters (e.g., thenumber, frequency, type and/or timing of transmission of advertisementsignals and the values of N, M and X) to be employed by the implantabledevice 104 to communicate with the external device 116 are defined.

According to this embodiment, the ED connectivity monitoring component204 can monitor or log advertisement signal information regarding anumber of advertisement signals received by the external device 116. Forexample, the ED connectivity monitoring component 204 can monitor or logadvertisement signal information regarding a number of advertisementsignals received by the external device 116 over a defined time period(e.g., 24 hours). The ED connectivity monitoring component 204 can alsoassociate a timestamp received by one or more of the advertisementsignals from the implantable device 104. In some implementations, the EDconnectivity monitoring component 204 can also monitor the types ofadvertisement signals that are received (e.g., alert or non-alert).

In other embodiments, the ED connectivity monitoring component 204 isconfigured to monitor telemetry connectivity information related tosuccessful telemetry connection sessions established between theexternal device 116 and the implantable device 104, referred to hereinas “telemetry session information.” For example, as described above,based on reception of an advertisement signal from the implantabledevice 104, the external device 116 and the implantable device 104 canestablish a successful telemetry session. For instance, the externaldevice 116 can send the implantable device 104 a response to theadvertisement signal informing the implantable device 104 that theadvertisement signal was received (e.g., an acknowledgment signal).Based on reception of the response by the implantable device 104, theimplantable device 104 and the external device 116 can establish atelemetry session send and/or receive data packets between one anotherin accordance with defined applications of the respective devices anddefined telemetry communication protocols employed by the respectivedevices. In another example, based on reception of an alertadvertisement signal, the external device 116 can establish a telemetryconnection/session with the implantable device 104 to read informationfrom the implantable device 104 (e.g., using an interrogation messageand associated protocol). For instance, the implantable device 104 canprovide the external device 116 with requested information (e.g.,biometric information sensed by the implantable device 104, telemetryconnectivity integrity information monitored by the implantable device104, etc.) in response to an interrogation message sent by the externaldevice 116 to the implantable device 104 requesting the information.

In another example, based on reception of a non-alert advertisementsignal, when the external device 116 has information to send to theimplantable device 104, the external device 116 can establish atelemetry connection/session with the implantable device 104 and providethe information to the implantable device 104. For instance, theexternal device 116 can provide the external device 116 withconfiguration or re-configuration information for application by theimplantable device 104. After the respective devices have receivedand/or transmitted the specific data packets associated with thetelemetry connection/session in accordance with the defined telemetrycommunication protocols employed by the respective devices, thetelemetry communication session is ended. The implantable device 104then returns to transmitting advertisement signals according to thedefined telemetry communication protocol employed.

In some implementations, the external device 116 can attempt toestablish a successful telemetry session with the implantable device 104each time the external device 116 receives an advertisement signal fromthe implantable device 104. In other embodiments, the external device116 can selectively respond to advertisement signals received from theimplantable device 104 according to the configuration and application ofthe external device 116 in accordance with the defined telemetrycommunication protocol employed by the external device 116. Anunsuccessful telemetry communication session refers to an inability forthe external device 116 and the implantable device 104 to establish asuccessful telemetry session after the external device 116 receivesand/or responds to an advertisement signal provided by the implantabledevice 104. For example, an unsuccessful telemetry session can include afailure, by the implantable device 104 and/or the external device 116 toperform telemetry communication according to the defined telemetrycommunication protocol following an attempt, by the external device 116or the implantable device 104, to establish a telemetry session with theimplantable device 104 or the external device, respectively.

In accordance with these embodiments, the ED connectivity monitoringcomponent 204 can monitor or log telemetry connectivity informationidentifying one or more times a successful telemetry session isestablished between the external device 116 and the implantable device104 over a defined time period (e.g., a 24 hour period). In someimplementations, the ED connectivity monitoring component 204 can alsotime stamp the successful telemetry sessions and identify the duration(e.g., start time and end time) of the successful telemetry sessions.The ED connectivity monitoring component 204 can also log the occurrenceof failed or unsuccessful telemetry sessions following an attempt, bythe external device 116 and/or the implantable device 104, to establisha telemetry connection session. For example, the ED connectivitymonitoring component 204 can monitor responses sent by the externaldevice 116 to the implantable device 104 following reception of anadvertisement signal by the external device 116, and whether asuccessful telemetry session was established between the implantabledevice 104 and the external device 116 based on the sending of therespective responses.

In another example, the ED connectivity monitoring component 204 canmonitor interrogation signal information identifying when interrogationrequests are sent by the external device 116 to the implantable device104 and whether the external device 116 received a response to therespective interrogation requests. In yet another example, the EDconnectivity monitoring component 204 can monitor transmission ofconfiguration or re-configuration information by the external device 116to the implantable device 104, and whether the external device 116receives an acknowledgment message, from the implantable device 104,confirming that the configuration information was received and appliedby the implantable device 104.

The ED connectivity monitoring component 204 can also monitor or logRSSI information associated with strengths of signals received by theexternal device 116 from the implantable device 104 and throughput ofdata packets received from the implantable device 104. For example, theED connectivity monitoring component 204 can monitor strengths ofadvertisement signals received by the external device 116 from theimplantable device 104. In another example, after the external device116 and the implantable device 104 have established a successfultelemetry session, the ED connectivity monitoring component 204 canmonitor strengths of data downlink packets received from the implantabledevice 104 and throughput of the downlink data packets. The EDconnectivity monitoring component 204 can also monitor throughput ofuplink packets transmitted by the external device 116 to the implantabledevice 104.

FIG. 3 illustrates a block diagram of an example, non-limiting table(e.g., table 300 including telemetry connectivity information monitoredby an external device in accordance with one or more embodimentsdescribed herein. Table 300 includes example telemetry connectivityinformation monitored by the ED connectivity monitoring component 204 inaccordance with embodiments described herein. In the embodiment shown intable 300, the ED connectivity monitoring component 204 monitoredtelemetry connectivity information for the external device 116 over a 24hour time period (e.g., time 00:00 to time 24:00 using a 24 hour clock),wherein 10 advertisement signals were received by the external device116. The first advertisement signal was received at time 10:12 and thetenth advertisement signal was received at time 22:55. It should beappreciated however that the information included in table 300 is merelyexemplary. For example, although table 300 demonstrates 10 advertisementsignals being received by the external device 116 from times 10:12 to22:55, it should be appreciated that the external device 116 can receiveless or more advertisement signals at different times throughout a 24hour period. In addition, the number of alert verses non-alertadvertisement signals can vary, the number of connections establishedcan vary, the RSSI can vary, etc.

For instance, in one embodiment, based on the telemetry communicationprotocol scheme employed by the external device 116 and the implantabledevice 104, the implantable device 104 is configured to send about 480advertisement signals within a 24 hour period. Based on variousconfiguration settings of the external device, the external device 116is expected to hear an advertisement signal about 3 percent of the timewhen the external device 116 and the implantable device 104 are withintransmission range of one another. In practice, the external device 116and the implantable device 104 are expected to be within transmissionrange of one another for about eight hours of the 24 hour period.According to this embodiment, the external device 116 is expected toreceive/detect about five advertisement signals within a 24 hour period.As such, reception/detection of less or much less than fiveadvertisement signals within a 24 hour period can indicate aconnectivity issue. While this embodiment has been described withreference to specific values and methodologies, the disclosure andembodiments described herein are not so limited. In fact, in variousdifferent embodiments, any number of different values or methodologiescan be employed and all such variations are within the scope of thedisclosure.

In addition to identifying when respective advertisement signals arereceived by the external device 116 over a 24 hour time period, table300 also includes information identifying the type of advertisementsignal received (e.g., alert verses non-alert), whether a successfultelemetry session or connection was established between the externaldevice 116 and the implantable device 104 based on the receivedadvertisement signal, and RSSI associated with the receivedadvertisement signals (and other possible received signals). Forexample, the external device 116 received four alert advertisementsignals, signals 1, 5, 7 and 9. Among these alert signals, successfultelemetry connections/sessions were established between the externaldevice 116 and the implantable device 104 for signals 1, 5, and 9. Theexternal device 116 also established a successful telemetry session withthe implantable device based on reception of non-alert signal 10.

For signals 1, 5, and 9, table 300 also includes information identifyingwhether an interrogation was sent, whether it was successful (e.g.,whether the external device received a response from the implantabledevice 104 with requested information), and the average throughput ofthe response to successful interrogations. As seen in table 300,although a connection was established and an interrogation was sentbased on reception of signal 9, the interrogation was unsuccessful. Forsuccessful interrogations, table 300 also includes throughputinformation (e.g., throughput of downlink information received inresponse to the interrogation request). Table 300 also includesthroughput information associated with uplink information provided bythe external device 116 to the implantable device 104 followingreception of non-alert signal 10.

Referring back to FIGS. 1 and 2, in various embodiments, the EDconnectivity assessment component 206 is configured to evaluate theintegrity and/or quality of telemetry connectivity between the externaldevice 116 and the implantable device 104 based on telemetryconnectivity information monitored by the ED connectivity monitoringcomponent 204. For example, the ED connectivity assessment component 206can analyze the telemetry connectivity information monitored by the EDconnectivity monitoring component 204 and determine whether a telemetryconnectivity error condition exists between the external device 116 andthe implantable device 104. In some implementations, described infra,the ED connectivity assessment component can also evaluate the integrityand/or quality of telemetry connectivity between the external device 116and the implantable device 104 based on telemetry connectivityinformation monitored by the implantable device 104 (e.g., via IDconnectivity monitoring component 404 discussed with respect to FIG. 4).

In one embodiment, the ED connectivity assessment component 206 isconfigured to determine whether the external device 116 and theimplantable device 104 are experiencing a telemetry connectivity errorcondition based on an amount of advertisement signals received by theexternal device 116 from the implantable device 104 within a definedtime period. According to this embodiment, the ED connectivityassessment component 206 can analyze the monitored telemetryconnectivity information after passage of the defined time period. Forexample, the implantable device 104 can transmit N (e.g., 480)advertisement signals within a defined time period of X hours (e.g., 24hours). The ED connectivity assessment component 206 can furtherdetermine that the external device 116 and the implantable device 104are experiencing a telemetry connectivity error condition if the numberof the advertisement signals received by the external device 116 withinthe defined time period is below a threshold value (e.g., 5, 10, 20,etc.). In another example, the ED connectivity assessment component 206can determine that a telemetry connectivity error condition associatedwith telemetry communication between the external device 116 and theimplantable device 104 exists based on the number of advertisementsignals received by the external device 116 exceeding the thresholdvalue or another threshold value.

In another embodiment, the ED connectivity assessment component 206 isconfigured to determine whether the external device 116 and theimplantable device 104 have a connectivity problem based on timing ofadvertisement signals received by the external device 116 from theimplantable device 104. According to this embodiment, the EDconnectivity assessment component 206 can regularly analyze themonitored telemetry connectivity information as it is received. Forexample, when the implantable device 104 is configured to transmitadvertisement signals at a particular frequency (e.g., about one signalper minute), the ED connectivity assessment component 206 can determinethat the external device 116 and the implantable device 104 have atelemetry connectivity problem if the frequency of the advertisementsignals received by the external device 116 falls above or below theparticular frequency (e.g., with respect to a defined deviationthreshold). In another example, when the implantable device 104 isconfigured to transmit advertisement signals according to a defined timeschedule, the ED connectivity assessment component 206 can determinethat telemetry communication between the external device 116 and theimplantable device 104 is associated with a telemetry connectivity errorcondition if the external device 116 fails to receive advertisementsignals from the implantable device 104 in accordance with the definedtime schedule.

In some implementations, the ED connectivity assessment component 206can also analyze type of advertisement signal received to identifyconnectivity issues. With these implementations, the amount, frequencyand/or timing of alert signals and non-alert signals for transmissionimplantable device 104 within a defined time period can be defined. TheED connectivity assessment component 206 can identify connectivityissues based on the amount, frequency, and/or timing of received alertadvertisement signals and/or the non-alert advertisement signals by theexternal device 116 from the implantable device 104 failing to complywith the defined parameters for reception of these signals. The EDconnectivity assessment component 206 can also be configured todetermine whether the external device 116 and the implantable device 104have a connectivity problem based on an amount of successful telemetrysessions established between the external device 116 and the implantabledevice 104 with a defined time period (e.g., 1 hour, 3 hours, 12 hours,24 hours, etc.). For example, when the implantable device 104 and theexternal device 116 are configured to establish about M successfultelemetry session within the defined time period, the ED connectivityassessment component 206 can determine that that the external device 116and the implantable device 104 have a telemetry connectivity problem ifthe external device 116 and the implantable device establish less than athreshold number (e.g., M or another number) of successful telemetrysessions within the defined time period.

In another implementation, the ED connectivity assessment component 206can identify occurrence of a telemetry connectivity error conditionassociated with performance of telemetry communication between theexternal device 116 and the implantable device 104 based on an amount ofsuccessful telemetry sessions established between the implantable device104 and the external device 116 within a defined period of time relativeto an amount of advertisement signals received by the external devicewithin the defined period of time. For example, the ED connectivityassessment component 206 can determine that a connectivity errorcondition exists based on a determination that a ratio or percentage ofthe amount of successful telemetry sessions established relative to theamount of advertisement signals received is below a threshold ratio orthreshold percentage (e.g., 25%, 15%, 10%, 5%, 3%, etc.). The EDconnectivity assessment component 206 can similarly compare a ratio ofsuccessful telemetry connections established relative to an amount ofalert or non-alert advertisement signals received to a threshold ratioor percentage to identify a connectivity issue.

Similarly, the ED connectivity assessment component 206 can determinewhether the external device 116 and the implantable device 104 have aconnectivity problem based on an amount of successful interrogationssent be the external device 116 to the implantable device 104 within adefined time period (wherein a successful interrogation refers toreception, by the external device 116, of information requested from theimplantable device 104). For example, the ED connectivity assessmentcomponent 206 can determine that a telemetry communication errorcondition exists between the external device 116 and the implantabledevice 104 based on a number of successful interrogations during adefined time period relative to a threshold amount. For example, the EDconnectivity assessment component 206 can determine that telemetrycommunication between the external device 116 and the implantable device104 is affected by a connectivity error condition in cases in which theinterrogation success rate for a defined time period falls below athreshold value. According to this example, the interrogation successrate can refer to number of successful interrogations relative to numberof alert advertisement signals received, or number of successfulinterrogations relative to number of interrogation requests sent.

In various additional embodiments, the ED connectivity assessmentcomponent 206 can also determine whether a telemetry connectivity errorcondition associated with telemetry communication between the externaldevice 116 and the implantable device 104 exists based on RSSIinformation for signals received by the external device 116 from theimplantable device 104. For example, the ED connectivity assessmentcomponent 206 can determine that the external device 116 and theimplantable device 104 have a telemetry connectivity problem based onthe RSSI information indicating the average strength of signals receivedby the external device 116 from the implantable device 104 within adefined time period is below a threshold value. In another example, theED connectivity assessment component 206 can identify occurrence oftelemetry connectivity error conditions based on a drop in strengths ofsignals received by the external device 116 from the implantable device104. In another example, the ED connectivity assessment component 206can identify connectivity problems based on identification of adistinguishable pattern associated with strengths of different signalsreceived by the external device 116 from the implantable device 104 thatare indicative of a connectivity problem. In yet another example, the EDconnectivity assessment component 206 can determine that the externaldevice 116 and the implantable device 104 have a telemetry connectivityproblem based on significant variation (e.g., with respect to a definedvariation range) in RSSI information for different signals received bythe external device 116 within a defined time period.

In another embodiment, the ED connectivity assessment component 206 candetermine whether the external device 116 and the implantable device 104have a connectivity problem based on throughput of downlink data packetsreceived by the external device 116 from the implantable device 104, anduplink data packets sent by the external device 116 to the implantabledevice. For example, the ED connectivity assessment component 206 candetermine that a connectivity error condition associated with telemetrycommunication between the external device 116 and the implantable device104 exists based on downlink throughput information indicating theaverage throughput of data packets received by the external device 116from the implantable device 104 within a defined time period is below athreshold value. In another example, the ED connectivity assessmentcomponent 206 can determine that the external device 116 and theimplantable device 104 have a telemetry connectivity problem based on adefined variation (e.g., with respect to a variation range) in downlinkthroughput information for different data packets received by theexternal device 116 within a defined time period. In another example,the ED connectivity assessment component 206 can determine that aconnectivity error condition associated with telemetry communicationbetween the external device 116 and the implantable device 104 existsbased on uplink throughput information indicating the average throughputof data packets transmitted by the external device 116 to theimplantable device 104 within a defined time period is below a thresholdvalue.

In some embodiments, the ED connectivity assessment component 206 canalso diagnose a cause of an identified telemetry connectivity problembased on telemetry connectivity information monitored by ED connectivitymonitoring component 204 (and in some implementations, based ontelemetry connectivity information monitored at the implantable device104 and provided to the external device 116 by the implantable device104). For example, based on the monitored telemetry connectivityinformation, the ED connectivity assessment component 206 can determinewhether a telemetry connectivity problem between the external device 116and the implantable device is attributed to a hardware malfunction atthe external device 116, a hardware malfunction at the implantabledevice 104, a software configuration problem at the external device 116,a software configuration problem at the implantable device 104, and/oran interference problem associated with the communication channelbetween the external device 116 and the implantable device 104. Inanother example, the ED connectivity assessment component 206 candetermine whether a telemetry connectivity problem is attributed tofailure of the external device 116 to be within telemetry transmissionrange of the implantable device 104 for a minimum amount of time (e.g.,8 hours) within a defined time period (e.g., 24 hours).

The ED notification component 208 facilitates notification to users (viauser devices) regarding a telemetry connectivity problem determined toexist between the external device 116 and the implantable device 104. Inone embodiment, the ED notification component 208 is configured togenerate a notification based on detection, by ED connectivityassessment component 206, of a telemetry connectivity problem betweenthe external device 116 and the implantable device 104. The notificationcan include information indicating the implantable device 104 and theexternal device 116 are experiencing a telemetry connectivity problem.In some embodiments, the notification can also include informationidentifying a cause of the telemetry connectivity problem or a potentialsolution to the telemetry connectivity problem. For example, manyidentified telemetry connectivity issues are attributed to failure ofthe external device 116 to remain within wireless transmission range ofthe implantable device 104 for a minimum amount of time within amonitored time period. According to this example, the notification caninclude information that instructs the wearer of the implantable device104 to move within transmission proximity of the external device 108 fora least a minimum amount of time.

In some implementations, the ED notification component 208 is furtherconfigured to present or render the notification at the external device116. For example, ED notification component 208 can present a visualnotification at the external device 116 that informs a user of theexternal device 116 (e.g., the wearer of the implantable device 104)regarding the connectivity problem. According to this example, thevisual notification can include text, an image, a symbol, etc.,presented via a display screen of the external device 116. In anotherexample, the visual notification can include an illuminated or blinkinglight at the external device 116 that indicates the connectivityproblem. In another example, the ED notification component 208 cangenerate an audible notification at the external device 116 via aspeaker of the external device 116 that informs the user regarding theconnectivity problem. For example, the notification can include an alarmor sound that requires manual interaction with the external device 116to disable the external device 116 (e.g., via the wearer of theimplantable device 104). Still in yet another example, the notificationcan include a vibration generated at the external device 116.

In another implementation, in addition or in the alternative torendering the notification at the external device 116, the EDnotification component 208 can send the notification to the serverdevice 122. For example, the server device 122 can be associated with aremote medical monitoring service that can inform a remote deviceassociated with a medical caregiver regarding the connectivity problembetween the implantable device 104 and the external device 116 based onreception of the notification from the ED notification component 208.

In some embodiments, the external device 116 and/or the implantabledevice 104 can be reconfigured to correct a telemetry connectivity errorcondition identified between the external device 116 and the implantabledevice 104 (e.g., as identified via the ED connectivity assessmentcomponent 206, the implantable device 104 via implantable device (ID)connectivity assessment component 406 discussed infra with respect toFIG. 4, and/or the server device 122 via SD connectivity assessmentcomponent 606, discussed infra with respect to FIG. 6). According tothese embodiments, the external device 116 can include ED configurationcomponent 212 to facilitate reconfiguring the external device 116 and/orthe implantable device 104 to correct the telemetry connectivityproblem.

In one embodiment, the ED configuration component 212 is configured toapply reconfiguration information received from the server device 122.According to this implementation, the server device 122 can determinehow to reconfigure the external device 116 including, but not limitedto, correct an identified telemetry connectivity problem between theimplantable device 104 and the external device 116 (e.g., via SDconfiguration component 612, as discussed infra with respect to FIG. 6).For example, the server device 122 can send the external device 116reconfiguration information that includes instructions regarding howexternal device 116 should be reconfigured. The external device 116 canalso receive a command from the server device 122 in association withreception of the reconfiguration information that instructs the externaldevice 116 to apply the reconfiguration information. In response toreception of the reconfiguration information and the command from theserver device 122, the ED configuration component 212 can apply thereconfiguration information. In another embodiment, the ED configurationcomponent 212 and/or the ED communication component 202 is configured torelay implantable device reconfiguration information, received from theserver device 122, to the implantable device 104.

In additional embodiments, in response to a determination (e.g., by theED connectivity assessment component 206) that a connectivity problembetween the external device 116 and/or the implantable device 104 isbased on telemetry communication protocol configuration settings of theexternal device 116 and/or the implantable device 104, the EDconfiguration component 212 or server device 122 can generateinformation to cause one or more configuration settings to be updated orthe ED configuration component 212 can generate information to cause oneor more operations to be altered.

For example, the ED configuration component 212 can modify a number ofdata packets per connection interval that the external device 116 shouldsend to the implantable device 104 and/or a number of data packets perconnection interval that the implantable device 104 should send theexternal device 116. In another example, the ED configuration component212 can change the duration of for which the implantable device 104 andthe external device 116 should maintain a connection in association withan established telemetry session (i.e., modify the connection interval).

In one embodiment, the ED configuration component 212 can furtherautomatically update telemetry communication protocol parametersemployed by the external device 116 and/or the implantable device 104based on the mechanisms determined to correct the telemetrycommunication protocols employed by the respective devices. For example,the ED configuration component 212 can direct the external device 116 toupdate its telemetry communication protocol settings to increase aconnection interval between the external device 116 and the implantabledevice 104. Including, but not limited to, updating the telemetrycommunication protocols employed by the implantable device 104, the EDconfiguration component 212 can send the implantable device 104reconfiguration information that defines how the implantable deviceshould update its telemetry protocol parameters. The reconfigurationinformation can further direct the implantable device 104 to apply thereconfiguration information to update its telemetry protocol settings.

FIG. 4 illustrates a block diagram of an example, non-limitingimplantable device (e.g., implantable device 104) for which integrity oftelemetry connectivity with an external device is monitored inaccordance with one or more embodiments described herein. Theimplantable device 104 includes implantable device (ID) communicationcomponent 402, an ID connectivity monitoring component 404, an IDconnectivity assessment component 406, an ID notification component 408,an ID reporting component 410, and an ID configuration component 412. Invarious embodiments described herein, the components of implantabledevice 104 can perform same or similar functions as the correspondingcomponents of the external device 116. For example, with reference toFIGS. 2 and 4, the ID communication component 402 can perform same orsimilar functions as ED communication component 202, the ID connectivitymonitoring component 404 can perform same or similar functions as EDconnectivity monitoring component 204, the ID connectivity assessmentcomponent 406 can perform same or similar functions as ED connectivityassessment component 206, the ID notification component 408 can performsame or similar functions as the ED notification component 208, the IDreporting component 410 can perform same or similar functions as the EDreporting component 210, and the ID configuration component 412 canperform same or similar functions as the ED configuration component 212.

One or more of the components of implantable device 104 constitutemachine-executable component(s) embodied within machine(s), e.g.,embodied in one or more computer readable mediums (or media) associatedwith one or more machines. Such component(s), when executed by the oneor more machines, e.g., computer(s), computing device(s), virtualmachine(s), etc. can cause the machine(s) to perform the operationsdescribed. The implantable device 104 can include ID memory 414 forstoring the computer executable components and instructions, and IDprocessor 416 to facilitate operation of the computer executablecomponents and instructions by implantable device 104. The implantabledevice 104 can include an ID bus 418 that couples the various componentsof the implantable device 104, including, but not limited to, the IDcommunication component 402, the ID connectivity monitoring component404, the ID connectivity assessment component 406, the ID notificationcomponent 408, the ID reporting component 410, the ID configurationcomponent 412, the ID processor 416 and/or the ID memory 414. Repetitivedescription of like elements employed in other embodiments describedherein is omitted for sake of brevity.

With reference to FIGS. 1, 2 and 4, similar to the ED communicationcomponent 202, the ID communication component 402 can facilitatetelemetry communication between the implantable device 104 and theexternal device 116. For example, the ID communication component 402 caninclude or be various hardware and software devices associated withestablishing and/or conducting a telemetry communication between theimplantable device 104 and the external device 116. For example, IDcommunication component 402 can control operation of atransmitter-receiver or transceiver (not shown) of the implantabledevice 104 to establish a telemetry session with the external device 116and to control transmission and reception of signals or data packetsbetween the implantable device 104 and the external device 116.

The ID communication component 402 can facilitate telemetrycommunication between the implantable device 104 and the external deviceusing a variety of telemetry communication protocols. For example, theID communication component 402 can communicate with the external device116 using communication protocols including, but not limited to, a NFCbased protocol, a BLUETOOTH® technology-based protocol, a ZigBee® basedprotocol, a WirelessHART® based protocol, a Z-Wave® based protocol, anANT based protocol, an RF based communication protocol, an IP basedcommunication protocol, a cellular communication protocol, a UWBtechnology-based protocol, or other forms of communication includingboth proprietary and non-proprietary communication protocols.

In various embodiments, the ID communication component 402 is configuredto control transmission and reception of information between theimplantable device 104 and the external device 116 via a telemetrycommunication link (e.g., telemetry communication link 118) facilitatedby a communication protocol utilizing lower energy consumption than aconventional communication protocol for wirelessly transmitting data. Ina non-limiting example, the ID communication component 402 controlstransmission and reception of signals and data packets between theimplantable device 104 and the external device 116 using BLE protocol.

Similar to the ED connectivity monitoring component 204, the IDconnectivity monitoring component 404 is configured to monitor telemetryconnectivity information associated with the integrity and quality oftelemetry connectivity between the implantable device 104 and theexternal device 116. For example, after establishing an initialconnection with the external device 116, pairing with the externaldevice 116, or otherwise establishing an authorized telemetrycommunication link (e.g., a telemetry communication link 118) with theexternal device 116, the ID connectivity monitoring component 404 canmonitor telemetry connectivity information associated with telemetrycommunication between the implantable device 104 and the external device116 over the course of operation of the implantable device 104. Inanother example, the ID connectivity monitoring component 404 canmonitor telemetry connectivity information associated with telemetrycommunication between the implantable device 104 and the external device116 according to a temporal cycle or schedule. For instance, the IDconnectivity monitoring component 404 can monitor or track telemetryconnectivity information for a defined period of time each hour, 3hours, 12 hours, 24 hours, etc. In yet another example, the IDconnectivity monitoring component 404 can randomly monitor telemetryconnectivity information associated with telemetry communication betweenthe implantable device 104 and the external device 116.

Still in yet another example, the ID connectivity monitoring component404 can monitor telemetry connectivity information in response to arequest command received from the external device 116. According to thisexample, the request can be associated with a request to perform anassessment on the quality and integrity of telemetry connectivitybetween the implantable device 104 and the external device 116. Therequest can define a type of telemetry connectivity information for theID connectivity monitoring component 404 to monitor and period of timeover which the ID connectivity monitoring component 404 is to monitorthe telemetry connectivity information. In one embodiment, the requestcommand can be issued based on user input at the external device 116identifying the type of telemetry connectivity information for the IDconnectivity monitoring component 404 to monitor and the time periodover which ID connectivity monitoring component 404 should monitor thetelemetry connectivity information. In another implementation, therequest command can be issued by the server device 122. According tothis implementation, the request command can be transmitted by theserver device 122 to the external device 116 via communication link 120and further related by the external device 116 to the implantable device104 via telemetry communication link 118.

In some embodiments, the implantable device 104 can log or store thetelemetry connectivity information monitored by the ID connectivitymonitoring component 404 in ID memory 414. The ID connectivitymonitoring component 404 can remove all or portions of the loggedtelemetry connectivity information over time for replacement with newtelemetry connectivity information. In other embodiments, in addition orin the alternative to storing the telemetry connectivity information inID memory 414, the implantable device 104 can send the monitoredtelemetry connectivity information to the external device 116 and/or theserver device 122 via ID reporting component 410 and/or ID communicationcomponent 402. According to these embodiments, the telemetryconnectivity information monitored by the ID connectivity monitoringcomponent 404 can be employed by the external device 116 and/or theserver device 122 for analysis and evaluation of telemetry connectivityproblems between the implantable device 104 and the external device 116.

For example, the ID reporting component 410 and/or the ID communicationcomponent 402 can send telemetry connectivity information monitored bythe ID connectivity monitoring component 404 to the external device 116according to a defined schedule (e.g., once an hour, once a day, twice aday, etc.). In another example, the ID reporting component 410 and/orthe ID communication component 402 can send telemetry connectivityinformation monitored by the ID connectivity monitoring component 404 tothe external device 116 in response to a request (e.g., an interrogationrequest), received from the external device 116 for the telemetryconnectivity information. The external device 116 can further forwardtelemetry connectivity information received from the implantable device104 to the server device 122 (e.g., via ED reporting component 210and/or ED communication component 202).

In one exemplary embodiment, the ID connectivity monitoring component404 is configured to monitor telemetry connectivity informationassociated with transmission of advertisement signals from theimplantable device 104 to the external device 116, (also referred toherein as advertisement signal information). As described supra, thenumber, frequency, type and/or timing of transmission of theadvertisement signals can be defined and can vary from time to time.According to this embodiment, the ID connectivity monitoring component404 can monitor or log advertisement signal information regardingnumber, frequency, type and/or timing of advertisement signalstransmitted by the implantable device 104. For example, the IDconnectivity monitoring component 404 can monitor or log advertisementsignal information regarding a number of advertisement signalstransmitted by the implantable device 104 over a defined time period(e.g., 24 hours). The ID connectivity monitoring component 404 can alsoassociate a timestamp with each advertisement signal transmitted by theimplantable device 104. The ID connectivity monitoring component 401 canalso identify the types (e.g., alert or non-alert) of advertisementsignals sent.

In other embodiments, the ID connectivity monitoring component 404 isconfigured to monitor telemetry connectivity information related toamount, frequency and/or timing of successful telemetry connectionsessions established between the implantable device 104 and the externaldevice 116. Similarly, the ID connectivity monitoring component 404 canalso log the amount, frequency, and/or timing of failed or unsuccessfultelemetry sessions following an attempt, by the external device 116and/or the implantable device 104, to establish a telemetry connectionsession. The ID connectivity monitoring component 404 can also monitoror log RSSI information associated with strengths of signals received bythe implantable device 104 from the external device 116, throughput ofdownlink data packets received from the external device 116, andthroughput of uplink data packets transmitted to the external device116. For example, the ID connectivity monitoring component 404 canmonitor strengths of advertisement response signals received from theexternal device 116. In another example, after the external device 116and the implantable device 104 have established a successful telemetrysession, the ID connectivity monitoring component 404 can monitorstrengths of data packets received from the external device 116 andthroughput of the data packets.

FIG. 5 illustrates a block diagram of an example, non-limiting table(e.g., table 500) including telemetry connectivity information monitoredby an implantable device (e.g., implantable device 104) in accordancewith one or more embodiments described herein. The table 500 includessome example telemetry connectivity information monitored by the IDconnectivity monitoring component 404 in accordance with embodimentsdescribed herein. In the embodiment exemplified in table 500, the IDconnectivity monitoring component 404 monitored telemetry connectivityinformation for the implantable device 104 over a 24 hour time period(e.g., time 00:00 to time 24:00 using a 24 hour clock), wherein 20advertisement signals were transmitted by the implantable device 104.The first advertisement signal was transmitted at time 10:05 and thetenth advertisement signal was received at time 22:51. It should beappreciated however that the information included in table 500 is merelyexemplary. For example, although table 500 demonstrates 20 advertisementsignals being transmitted from the implantable device from times 10:05to 22:51, it should be appreciated that the implantable device 104 cantransmit different amounts of advertisement signals at different timesthroughout a 24 hour period. For example, in one embodiment, theimplantable device 104 is configured to transmit between 300 and 600advertisement signals a day. In another embodiment, the implantabledevice 104 is configured to transmit between 450 and 550 advertisementsignals a day. In yet another embodiment, the implantable device 104 isconfigured to transmit about 480 advertisement signals a day. Inaddition, the number of alert verses non-alert advertisement signals canvary, the number of connections established can vary, the RSSI can vary,etc.

In addition to identifying when respective advertisement signals aresent by the implantable device 104 over a 24 hour time period, table 500also includes information identifying the type of advertisement signalreceived (e.g., alert verses non-alert), and whether a successfultelemetry session or connection was established between the externaldevice 116 and the implantable device 104 based on the transmittedadvertisement signal. For example, successful telemetry sessions wereestablished between the external device 116 and the implantable device104 based on transmission of advertisement signals 1, 9, 17 and 19. Forconnections based on signals 1 and 9, interrogations signals werereceived and responded to by implantable device 104. For these signalsinformation is recorded that identifies RSSI associated with signalsreceived from the external device 116 (e.g., the interrogationrequests), and throughput of interrogation response data packetstransmitted by the implantable device 104. Although a connection wasestablished and an interrogation response was received for signal 17,due to some reason (e.g., an error condition such as low RSSI associatedwith the interrogation request), the implantable device 104 did not senda response. Table 500 also shows that a connection was established basedon non-alert signal 19. For this signal, the implantable device 104recorded RSSI and throughput for downlink information received from theexternal device 116.

Referring back to FIGS. 1, 2 and 4, in some embodiments, the IDconnectivity assessment component 406 is configured to evaluate theintegrity and/or quality of telemetry connectivity between the externaldevice 116 and the implantable device 104 based on the telemetryconnectivity information monitored by the ID connectivity monitoringcomponent 404. In other embodiments, the implantable device 104 isconfigured to send telemetry connectivity information monitored by theID connectivity monitoring component 404 to the external device 116and/or the server device 122 for evaluation. Still in other embodiments,the ID connectivity assessment component 406 is configured to evaluatethe integrity and/or quality of telemetry connectivity between theexternal device 116 and the implantable device 104 based on thetelemetry connectivity information monitored by the ID connectivitymonitoring component 404 and telemetry connectivity informationmonitored by the ED connectivity monitoring component 204 and sent tothe implantable device 104 by the external device 116.

For example, based on monitored telemetry connectivity information(e.g., monitored by the ED connectivity monitoring component 204 and/orthe ID connectivity monitoring component 404), the ID connectivityassessment component 406 can determine whether the implantable device104 and the external device 116 have established or maintainedestablishment of telemetry communication link 118. In another example,the ID connectivity assessment component 406 can determine whether therespective devices can receive data packets from one another withsufficient throughput and/or signal strength via the telemetrycommunication link 118. In yet another example, the ID connectivityassessment component 406 can determine whether the respective devicescan transmit and/or receive information to/from one another via thetelemetry communication link 118 according to a defined communicationscheme, schedule, or mode of operation.

In one embodiment, the ID connectivity assessment component 406 isconfigured to determine whether a connectivity error conditionassociated with telemetry communication between the implantable device104 and the external device 116 exists based on an amount ofadvertisement signals transmitted by the implantable device 104 within adefined time period. According to this embodiment, the ID connectivityassessment component 406 can analyze the monitored telemetryconnectivity information after passage of the defined time period. Forexample, the implantable device 104 can transmit N (e.g., 480)advertisement signals within a defined time period of X hours (e.g., 24hours) or minutes. The ID connectivity assessment component 406 candetermine that the external device 116 and the implantable device 104have a telemetry connectivity problem if the number of the advertisementsignals transmitted by the implantable device 104 within the definedtime period is below a threshold value (e.g., N or another number). Inanother example, the ID connectivity assessment component 406 candetermine that the external device 116 and the implantable device 104have a telemetry connectivity problem if the number of advertisementsignals transmitted by the implantable device within the defined timeperiod exceeds the threshold value or another threshold value.

In another embodiment, the ID connectivity assessment component 406 isconfigured to determine whether the external device 116 and theimplantable device 104 have a connectivity problem based on timing ofadvertisement signals transmitted by the implantable device 104.According to this embodiment, the ID connectivity assessment component406 can regularly analyze the monitored telemetry connectivityinformation as it is received or determined. For example, when theimplantable device 104 is configured to transmit advertisement signalsat a particular frequency (e.g., about one signal per minute), the IDconnectivity assessment component 406 can determine that the externaldevice 116 and the implantable device 104 have a telemetry connectivityproblem if the frequency of the advertisement signals transmitted by theimplantable device 104 falls significantly above or below the particularfrequency (e.g., with respect to a defined deviation threshold). Inanother example, when the implantable device 104 is configured totransmit advertisement signals according to a defined time schedule, theID connectivity assessment component 406 can determine that the externaldevice 116 and the implantable device 104 have a telemetry connectivityproblem if the implantable device 104 fails to transmit theadvertisement signals in accordance with the defined time schedule.

In some implementations, the ID connectivity assessment component 406can also analyze type of advertisement signal transmitted to identifyconnectivity issues. With these implementations, the amount, frequencyand/or timing of alert signals and non-alert signals for transmissionwithin a defined time period can be defined. The ID connectivityassessment component 406 can identify connectivity issues based on theamount, frequency, and/or timing of transmitted alert advertisementsignals and/or the non-alert advertisement signals by the implantabledevice 104 failing to comply with the defined parameters for receptionof these signals (e.g., being above or below respective thresholdamounts for the different types of advertisement signals).

In another exemplary embodiment, the ID connectivity assessmentcomponent 406 can also be configured to detect occurrence of a telemetryconnectivity error condition associated with telemetry communicationbetween the external device 116 and the implantable device 104 based onan amount of successful telemetry sessions established between theexternal device 116 and the implantable device 104 with a defined timeperiod (e.g., 1 hour, 3 hours, 12 hours, 24 hours, etc.). For example,when the implantable device 104 and the external device 116 areconfigured to establish M successful telemetry session within thedefined time period, the ID connectivity assessment component 406 candetermine that that the external device 116 and the implantable device104 have a telemetry connectivity problem if the external device 116 andthe implantable device establish less than a threshold number (e.g., Mor another number) of successful telemetry sessions within the definedtime period.

In one embodiment of this embodiment, the ID connectivity assessmentcomponent 406 is configured to determine whether the implantable device104 and the external device 116 have a telemetry connectivity problembased on a ratio or percentage corresponding to the number of successfultelemetry sessions established between the implantable device 104 andthe external device 116 relative to a number of advertisement signalstransmitted (e.g., alert signals and/or non-alert signals) by theimplantable device 104 within a defined time period. This ratio orpercentage is referred to herein as the “telemetry connectivity sessionsuccess rate.” For example, the implantable device 104 can have anexpected telemetry connectivity session success rate of Y percent (e.g.,2%, 3%, 5%, 10%, 15%, etc.). In an embodiment, the ID connectivityassessment component 406 is configured to determine that the implantabledevice 104 and the external device 116 have a telemetry connectivityproblem based on the telemetry connectivity success rate being below orsignificantly below (e.g., with respect to a threshold degree ofdeviation), a threshold telemetry connectivity session success rate.

Similarly, the ID connectivity assessment component 406 can determinewhether the external device 116 and the implantable device 104 have aconnectivity problem based on an amount of interrogations received bythe implantable device 104 from the external device 116 within a definedtime period. For example, the external device 116 can transmit about Ninterrogation requests to the implantable device 104 within a definedtime period. According to this example, the ID connectivity assessmentcomponent 406 can determine that the external device 116 and theimplantable device 104 have a telemetry connectivity problem if theamount of interrogation requests received by the implantable device 104from the external device within the defined time period falls below athreshold value (e.g., N or another number less than N). In anotherimplementation, the ID connectivity assessment component 406 isconfigured to determine whether a telemetry connectivity problem existsbetween the external device 116 and the implantable device 104 based ona ratio or percentage corresponding to the amount of interrogationsignals received by the implantable device 104 within a defined timeperiod relative to the amount of successful telemetry sessionsestablished between the external device and the implantable devicewithin the defined time period. For example, the ID connectivityassessment component can determine a connectivity error conditionassociated with telemetry communication between the external device 116and the implantable device 104 exists if this ratio or percentage isbelow a threshold ratio or threshold percentage.

In various additional embodiments, the ID connectivity assessmentcomponent 406 can also determine whether the external device 116 and theimplantable device have a telemetry connectivity problem based on RSSIinformation for signals received by the implantable device 104 from theexternal device 116. For example, the ID connectivity assessmentcomponent 406 can determine that the external device 116 and theimplantable device 104 have a telemetry connectivity problem based onthe RSSI information indicating the average strength of signals receivedby the implantable device 104 from the external device 116 within adefined time period is below a threshold value. In another example, theID connectivity assessment component 406 can determine that the externaldevice 116 and the implantable device 104 have a telemetry connectivityproblem based on significant variation (e.g., with respect to athreshold variation range) in RSSI information for different signalsreceived by the implantable device 104 within a defined time period.

In another embodiment, the ID connectivity assessment component 406 candetermine whether the external device 116 and the implantable device 104have a connectivity problem based on throughput of data packets receivedby the implantable device 104 from the external device 116. For example,the ID connectivity assessment component 406 can determine that theexternal device 116 and the implantable device 104 have a telemetryconnectivity problem based on throughput information indicating theaverage throughput of data packets received by the implantable device104 from the external device within a defined time period is below athreshold value. In another example, the ID connectivity assessmentcomponent 406 can determine that the external device 116 and theimplantable device 104 have a telemetry connectivity problem based onsignificant variation (e.g., with respect to a variation range) inthroughput information for different data packets received by theimplantable device within a defined time period.

In some embodiments, the ID connectivity assessment component 406 canalso diagnose a cause of an identified telemetry connectivity problembased on telemetry connectivity information monitored by the IDconnectivity monitoring component 404 (and in some implementations,additional telemetry connectivity information monitored by the EDconnectivity monitoring component 204).

With reference to FIGS. 1-5, in various embodiments, the telemetryconnectivity information monitored by the external device 116 (e.g., viaED connectivity monitoring component 204) and the implantable device 104(e.g., via ID connectivity monitoring component 404) can be combined andevaluated to determine whether a connectivity problem exists between theimplantable device 104 and the external device 116. The analysis of thecombined information can be performed at the external device 116 (e.g.,via ED connectivity assessment component 206), the implantable device104 (e.g., via ID connectivity assessment component 406), and/or at theserver device (e.g., via SD connectivity assessment component 606, asdiscussed infra with respect to FIG. 6). In instances in which analysisof the combined telemetry connectivity information is performed at theexternal device 116 and/or the server device 122, the implantable device104 can send the external device 116 telemetry connectivity informationmonitored by the ID connectivity monitoring component 404. For example,the implantable device 104 can report out monitored telemetryconnectivity information to the external device using ID reportingcomponent 410 and/or ID communication component 402. In embodiments inwhich the analysis of the combined telemetry connectivity information isperformed at the server device 122, the external device 116 can send(e.g., via ED reporting component 210 and/or ID communication component402) telemetry connectivity information received from the implantabledevice 104, and telemetry connectivity information monitored by the EDconnectivity monitoring component 204, to the server device 122 viacommunication link 120.

In accordance with these embodiments, the ED connectivity assessmentcomponent 206, the ID connectivity assessment component 406, and/or theSD connectivity assessment component 606, respectively, can comparemonitored ED telemetry connectivity information with monitored IDtelemetry connectivity information to determine whether the externaldevice 116 and the implantable device 104 have a telemetry connectivityproblem. In some embodiments, the respective connectivity assessmentcomponents can also determine a cause of an identified telemetryconnectivity problem (e.g., configuration problem, hardware problem,interference problem, etc.) based on comparison of the monitored EDtelemetry connectivity information with the monitored ID telemetryconnectivity information.

In one embodiment, the ED connectivity assessment component 206, the IDconnectivity assessment component 406, and/or the SD connectivityassessment component 606 can compare advertisement signal informationregarding number, frequency and timing of advertisement signalstransmitted by the implantable device 104 to the external device 116and/or number, frequency and time of advertisement signals received bythe external device 116 from the implantable device. The respectivetelemetry connectivity assessment components can further determine thata telemetry connectivity problem exists between the implantable device104 and external device 116 based on a degree of incongruency betweenthe information. For example, the respective telemetry connectivityassessment components can determine that a telemetry connectivityproblem exists between the implantable device 104 and the externaldevice when the number of advertisement signals transmitted by theimplantable device 104 does not correspond or sufficiently correspond(e.g., with respect to a threshold degree of deviation) to the number ofadvertisement signals received by the external device 116. In anotherexample, the respective telemetry connectivity assessment components candetermine that a telemetry connectivity problem exists between theimplantable device 104 and the external device 116 in cases in which thefrequency and/or timing of advertisement signals transmitted by theimplantable device 104 does not correspond or sufficiently correspond(e.g., with respect to a threshold degree of deviation) to the frequencyand/or timing of advertisement signals received by the external device116.

In another implementation, the ED connectivity assessment component 206,the ID connectivity assessment component 406, and/or the SD connectivityassessment component 606 can compare interrogation signal informationregarding number, frequency and timing of interrogation signalstransmitted by the external device to the implantable device 104 andnumber, frequency and time of interrogation signals received by theimplantable device 104 from the external device 116. The respectivetelemetry connectivity assessment components can further determine thata telemetry connectivity problem exists between the implantable device104 and the external device 116 in cases in which the number, frequencyand/or timing of interrogation signals transmitted by the externaldevice 116 does not correspond or sufficiently correspond (e.g., withrespect to a threshold degree of deviation) to the number, frequencyand/or timing of interrogation signals received by the implantabledevice 104.

Still in yet another implementation, the ED connectivity assessmentcomponent 206, the ID connectivity assessment component 406, and/or theSD connectivity assessment component 606 can compare RSSI informationfor signals received by the external device 116 from the implantabledevice 104 with RSSI information for other signals received by theimplantable device 104 from the external device 116. The respectivetelemetry connectivity assessment components can further determine thata telemetry connectivity problem exists between the implantable device104 and the external device 116 in cases in which the RSSI informationfor signals received by the external device 116 from the implantabledevice 104 does not correlate or sufficiently correlate (e.g., withrespect to a threshold degree of deviation) with the RSSI informationfor other signals received by the implantable device 104 from theexternal device 116.

Referring back to FIGS. 1, 2 and 4, similar to the ED notificationcomponent 208, the ID notification component 408 facilitates notifyingusers regarding a telemetry connectivity problems determined to existbetween the external device 116 and the implantable device 104. In oneembodiment, the ID notification component 408 is configured to generatea notification based on detection, by ID connectivity assessmentcomponent 406, of a telemetry connectivity problem between the externaldevice 116 and the implantable device 104. The notification can includeinformation indicating the implantable device 104 and the externaldevice 116 are experiencing a telemetry connectivity problem. In someembodiments, the notification can also include information identifying acause of the telemetry connectivity problem. In one embodiment, the IDnotification component 408 is further configured to send thenotification to the external device 116 for rendering or presenting atthe external device (e.g., via ED notification component 208). Inanother embodiment, the ID notification component can send thenotification to the external device 116 for forwarding, by the EDnotification component 208, to the server device 122. For example, theserver device 122 can be associated with a remote medical monitoringservice that can inform remote medical caregivers regarding theconnectivity problem between the implantable device 104 and the externaldevice 116 based on reception of the notification from the EDnotification component 208.

In some embodiments, the external device 116 and/or the implantabledevice 104 can be reconfigured to correct an identified telemetryconnectivity problem between the external device 116 and the implantabledevice 104 (e.g., as identified via the ID connectivity assessmentcomponent 406, the external device 116 via the ED connectivityassessment component 206, and/or the server device 122 via SDconnectivity assessment component 606, discussed infra with respect toFIG. 6). According to these embodiments, the implantable device 104 caninclude ID configuration component 412 to facilitate reconfiguring theexternal device 116 and/or the implantable device 104 to correct thetelemetry connectivity problem.

The ID configuration component 412 can perform same or similar functionsas the ED configuration component 212. For example, in one embodiment,the ID configuration component 412 is configured to applyreconfiguration information received from the external device 116.According to this embodiment, the external device 116 or the serverdevice 122 can determine how to reconfigure the implantable device 104to correct an identified telemetry connectivity problem between theimplantable device 104 and the external device 116. The external device116 or the server device 122 (e.g., using the external device 116 as arelay) can further send the implantable device reconfigurationinformation that includes instructions regarding how implantable device104 should be reconfigured. The implantable device 104 can also receivea command from the external device 116 in association with reception ofthe reconfiguration information that instructs the implantable device toapply the reconfiguration information. In response to reception of thereconfiguration information and the command from the external device116, ID configuration component 412 can apply the reconfigurationinformation.

In additional embodiments, in response to a determination (e.g., by theID connectivity assessment component 406) that a connectivity problembetween the external device 116 and the implantable device 104 is basedon telemetry communication protocol configuration settings of theexternal device 116 and/or the implantable device 104, the IDconfiguration component 412 can update one or more configurationsettings of the implantable device 104.

For example, the ID configuration component 412 can modify a number ofdata packets per connection interval that the external device 116 shouldsend to the implantable device 104 and/or a number of data packets perconnection interval that the implantable device 104 should send theexternal device 116. In another example, the ID configuration component412 can change the duration of for which the implantable device 104 andthe external device 116 should maintain a connection in association withan established telemetry session (i.e., modify the connection interval).

For example, the external device 116 (e.g., via ED connectivityassessment component 206) or the server device 122 (e.g., via SDconnectivity assessment component 606) can determine that a connectivityerror condition associated with telemetry communication between theimplantable device 104 and the external device 116 exists based on adetermination that an amount of advertisement signals received by theexternal device 116 from the implantable device 104 within a definedtime period is below a threshold amount. The external device 116 or theserver device 122 can further determine one or more operations tocorrect the connectivity error condition that involves reconfigurationof a telemetry communication protocol employed by the implantable device104. The external device 116 or the server device 122 (e.g., using theexternal device 116 as a relay) can further transmit reconfigurationinformation to the implantable device 104 that instructs the implantabledevice 104 to reconfigure the telemetry communication protocol settingaccordingly. The ID configuration component 412 can receive thereconfiguration information and reconfigure the communication protocolsemployed by the implantable device 104 accordingly.

The ID configuration component 412 can further automatically updatetelemetry communication protocol parameters employed by the implantabledevice 104 and/or the external device 116 based on the operationsdetermined to correct the telemetry communication protocols employed bythe respective devices. For example, the ID configuration component 412can direct the implantable device 104 to update its telemetrycommunication protocol settings to increase a connection intervalbetween the external device 116 and the implantable device 104.Including, but not limited to, updating the telemetry communicationprotocols employed by the external device 116, the ID configurationcomponent 412 can send the external device 116 reconfigurationinformation that defines how the external device 116 should update itstelemetry communication protocol parameters. The reconfigurationinformation can further direct the external device to apply thereconfiguration information to update its telemetry protocol settings.

FIG. 6 illustrates a block diagram of an example, non-limiting serverdevice (e.g., server device 122) in accordance with one or moreembodiments described herein. The server device 122 includes serverdevice (SD) communication component 602, SD connectivity monitoringcomponent 604, SD connectivity assessment component 606, SD notificationcomponent 608 and SD configuration component 610. In some embodiments,the respective components of server device 122 can perform same orsimilar functions as the corresponding external device 116 components.For example, the SD communication component 602 can perform same orsimilar functions as the ED communication component 202, the SDconnectivity monitoring component 604 can perform same or similarfunctions as the ED connectivity monitoring component 204, the SDconnectivity assessment component 606 can perform same or similarfunctions as the ED connectivity assessment component 206, the SDnotification component 608 can perform same or similar functions as theED notification component 208, and the SD configuration component 610can perform same or similar functions as the ED configuration component212.

One or more of the components of the server device 122 constitutemachine-executable component(s) embodied within machine(s), e.g.,embodied in one or more computer readable mediums (or media) associatedwith one or more machines. Such component(s), when executed by the oneor more machines, e.g., computer(s), computing device(s), virtualmachine(s), etc. can cause the machine(s) to perform the operationsdescribed. The server device 122 can include SD memory 614 configured tostore the computer executable components and instructions, and SDprocessor 616 to facilitate operation of the computer executablecomponents and instructions by the sever device 122. The external serverdevice 122 can include a SD bus 618 that couples the various componentsof the SD, including, but not limited to, the SD communication component602, the SD connectivity monitoring component 604, the SD connectivityassessment component 606, the SD notification component 608, the SDconfiguration component 612, the SD processor 216 and/or the SD memory614. Repetitive description of like elements employed in otherembodiments described herein is omitted for sake of brevity.

With reference to FIGS. 1 and 6, the SD communication component 602 isconfigured to facilitate communication between the server device 122 andthe external device 116 using various communication protocols andnetworks discussed with reference to FIG. 1 and communication link 120.For example, the SD communication component 602 can facilitate telemetrycommunication between the server device 122 and the external device 116using a wide-range wireless telemetry communication protocol such as anIP or cellular based communication protocol via a WAN. In anotherembodiment, the SD communication component 602 can facilitatecommunication between the external device 116 and the server device 122via a LAN (e.g., using a Wi-Fi based communication protocol) or a wiredconnection.

Similar to ED connectivity monitoring component 204 and ID connectivitymonitoring component 404, the SD connectivity monitoring component 604is configured to monitor information associated with the integrity andquality of telemetry connectivity between the external device 116 andthe implantable device 104, (i.e., telemetry connectivity information).In particular, the SD connectivity monitoring component 604 can monitoror track telemetry connectivity information regarding telemetryconnectivity between the external device 116 and the implantable device104 provided to the server device 122 from the external device 116and/or the implantable device 104. For example, in some embodiments, theexternal device 116 is configured to send (e.g., via ED reportingcomponent 210) the server device 122 telemetry connectivity informationmonitored by the ED connectivity monitoring component 204. In otherembodiments, the external device 116 is configured to send the serverdevice 122 telemetry connectivity information monitored by the IDconnectivity monitoring component 404 based on provision of thetelemetry connectivity information to the external device 116 by theimplantable device 104 (e.g., via ID reporting component 410). Accordingto these embodiments, the SD connectivity monitoring component 604 canmonitor or log the telemetry connectivity information received from theexternal device 116.

The SD connectivity assessment component 606 is configured to evaluatereceived telemetry connectivity information in a same or similar fashiondescribed with respect to ED connectivity assessment component 206and/or ID connectivity assessment component 406. In particular, the SDconnectivity assessment component 606 can evaluate the integrity and/orquality of telemetry connectivity between the external device 116 andthe implantable device 104 based on the received telemetry connectivityinformation monitored by the ED connectivity monitoring component 204and/or the ID connectivity monitoring component 404. In accordance withvarious embodiments, the SD connectivity assessment component 606 cananalyze the telemetry connectivity information to determine whether atelemetry connectivity error condition exists between the externaldevice 116 and the implantable device 104.

For example, in one exemplary embodiment, the SD connectivity assessmentcomponent 606 can analyze telemetry connectivity information includingadvertisement signal information regarding amount, timing and/orfrequency of advertisement signals received by the external device 116from the implantable device 104 and/or amount, timing and/or frequencyof advertisement signals sent by the implantable device 104 to theexternal device 116. For example, the SD connectivity assessmentcomponent 606 can determine that a telemetry connectivity errorcondition associated with performance of telemetry communication betweenthe external device 116 and the implantable device 104 exists based onan amount of advertisement signals received by the external device 116within a defined period of time being less than a threshold amount. Inanother example, the SD connectivity assessment component 606 candetermine that a telemetry connectivity error condition exists based onan amount of advertisement signals transmitted by the implantable device104 within a defined period of time is less than a threshold amount. Inanother example, the SD connectivity assessment component 606 candetermine that a telemetry connectivity error condition exists based ona degree of incongruency between an amount of advertisement signalstransmitted by the implantable device 104 to the external device 116 andanother amount of advertisement signals received by the external device116 from the implantable device.

In another exemplary embodiment, the SD connectivity assessmentcomponent 606 can analyze telemetry connectivity information regardingamount, timing and/or frequency of successful telemetry connectivitysessions established between the implantable device 104 and the externaldevice 116 (e.g., as logged by the external device 116 and/or theimplantable device 104). For example, the SD connectivity assessmentcomponent 606 can determine that a telemetry connectivity errorcondition associated with performance of telemetry communication betweenthe external device 116 and the implantable device 104 exists based onthe amount of successful telemetry sessions that occurred over a periodof time being below a threshold value. In another example, the SDconnectivity assessment component 606 can determine that a telemetryconnectivity error condition exists based on discrepancy between theamount of successful telemetry sessions identified by the externaldevice 116 over a period of time and another amount of successfultelemetry sessions identified be the implantable device over the periodof time. In another example, the SD connectivity assessment component606 can determine that a telemetry connectivity error condition existsbased on ratio representative of successful telemetry sessionsestablished between the external device 116 and the implantable device104 and an amount of advertisement signals received or transmitted bythe respective devices, being less than a threshold ratio.

Still in other exemplary embodiments, the SD connectivity assessmentcomponent 606 can analyze interrogation success rate information, RSSIinformation for the external device 116 and/or the implantable device104, and throughput information for the external device 116 and theimplantable device 104 to identify and/or diagnose telemetryconnectivity problems between the respective devices (e.g., inaccordance with the techniques described with respect to ED connectivityassessment component 206 and ID connectivity assessment component 406).

Similar to ED notification component 208, the SD notification component608 facilitates notifying users regarding a telemetry connectivityproblem determined to exist between the external device 116 and theimplantable device 104. In one embodiment, the SD notification component608 is configured to generate a notification based on a determinationthat a telemetry connectivity problem exists between the external device116 and the implantable device 104. The notification can includeinformation indicating the implantable device 104 and the externaldevice 116 are experiencing a telemetry connectivity problem. In someembodiments, the notification can also include information identifying acause of the telemetry connectivity problem. The SD notificationcomponent 608 can further render the notification at the server device122 and/or send the notification to another device. For example, the SDnotification component 608 can send (e.g., using SD communicationcomponent 602), the notification to the external device 116 forrendering at the external device. The SD notification component 608 canalso send the notification to the implantable device 104 (e.g., usingthe external device 116 as a relay), and/or send the notification toother suitable devices.

In some embodiments, the external device 116 and/or the implantabledevice 104 can be reconfigured to correct a telemetry connectivity errorcondition identified between the external device 116 and the implantabledevice 104. In some implementations, the SD configuration component 610is configured to facilitate reconfiguring the external device 116 and/orthe implantable device 104 to correct the telemetry connectivityproblem. For example, the SD configuration component 610 can determinehow to update the configuration settings of one or both of the devicesto correct the connectivity problem. In particular, the SD configurationcomponent 610 can determine a modification to one or more telemetrycommunication protocol parameters employed by the external device 116and/or the implantable device 104 that corrects the connectivityproblem. For example, the SD configuration component 610 can modify anumber of data packets per connection interval that the external device116 should send to the implantable device 104 and/or a number of datapackets per connection interval that the implantable device 104 shouldsend the external device 116. In another example, the SD configurationcomponent 610 can change the duration of for which the implantabledevice 104 and the external device 116 should maintain a connection inassociation with an established telemetry session (i.e., modify theconnection interval).

In one embodiment, the SD configuration component 610 can also send theexternal device 116 a command including reconfiguration information andthat instructs the external device 116 to reconfigure one or moreparameters of the telemetry communication protocol parameters employedby the external device 116. Based on reception of the command, theexternal device 116 can reconfigure its telemetry communication protocolparameters according to the reconfiguration information. In anotherimplementation, the SD configuration component 610 can send the externaldevice 116 a command including reconfiguration information directed tothe implantable device 104. The command can instruct the external device116 to send the reconfiguration information to the implantable device104. Based on reception of the command, the external device 116 can sendthe reconfiguration information to the implantable device 104 and basedon reception of the command from the external device 116, theimplantable device 104 can reconfigure its telemetry communicationprotocol parameters according to the reconfiguration information.

FIGS. 7-11 illustrate flow diagrams of example, non-limiting methods formonitoring integrity of telemetry connectivity between an implantabledevice and an external device in accordance with one or more embodimentsdescribed herein. While, for purposes of simplicity of explanation, themethodologies are shown and described as a series of acts, the disclosedsubject matter is not limited by the order of acts, as some acts canoccur in different orders and/or concurrently with other acts from thatshown and described herein. For example, those skilled in the art willunderstand and appreciate that a methodology can alternatively berepresented as a series of interrelated statuses or events, such as in astate diagram. Moreover, not all illustrated acts can be required toimplement a methodology in accordance with the disclosed subject matter.Additionally, it is to be appreciated that the methodologies disclosedin this disclosure are capable of being stored on an article ofmanufacture to facilitate transporting and transferring suchmethodologies to computers or other computing devices.

Referring now to FIG. 7, shown is a flow diagram of an example method700 for monitoring integrity of telemetry connectivity between animplantable device and an external device in accordance with oneembodiment. Various embodiments of method 700 can be performed by adevice including a processor, such as external device 116. In someembodiments of method 700, external device 116 employs ED communicationcomponent 202, ED connectivity monitoring component 204, ED connectivityassessment component 206 and/or ED notification component 208.Repetitive description of like elements employed in other embodimentsdescribed herein is omitted for sake of brevity.

At 702, a device including a processor (e.g., external device 116),monitors telemetry connectivity information including advertisementsignal information identifying times advertisement signals are receivedby the device from an implantable device (e.g., implantable device 104).At 704, the device determines whether a telemetry connectivity errorcondition exists associated with performing telemetry communicationbetween the device and the implantable device based on an amount of theadvertisement signals received within a defined time period relative toa threshold amount. At 706, the device generates a notificationidentifying the telemetry connectivity error condition based on adetermination that the telemetry connectivity error condition exists.For example, in one embodiment, the device determines that the telemetryconnectivity error exists based on the amount of the advertisementsignals received within the defined time period being below thethreshold amount. At 708, the device sends the notification to anotherdevice. For example, the device can send the notification to a serverdevice (e.g., server device 122) and/or the implantable device (e.g.,implantable device 104). In other embodiments, the device can render thenotification at the device.

Turning now to FIG. 8, shown is a flow diagram of another example method800 for monitoring integrity of telemetry connectivity between animplantable device and an external device in accordance with oneembodiment. Various embodiments of method 800 can be performed by adevice including a processor, such as external device 116. In someembodiments of method 800, external device 116 employs ED communicationcomponent 202, ED connectivity monitoring component 204, ED notificationcomponent 208 and/or ED reporting component 210. Repetitive descriptionof like elements employed in other embodiments described herein isomitted for sake of brevity.

At 802, a device including a processor (e.g., external device 116),monitors telemetry connectivity information including advertisementsignal information identifying times advertisement signals are receivedby the device from an implantable device (e.g., implantable device 104).At 804, the device sends the telemetry connectivity information to aserver device (e.g., server device 122). At 806, the device receives anotification indicating a telemetry connectivity error conditionassociated with telemetry performance between the device and theimplantable device exists based on a determination (e.g., made by theserver device 122) that an amount of the advertisement signals receivedby the device within a defined time period is less than a thresholdamount. At 808, the device renders the notification via a display of thedevice.

FIG. 9 shows a flow diagram of another example method 900 for monitoringintegrity of telemetry connectivity between an implantable device and anexternal device in accordance with one embodiment. Various embodimentsof method 900 can be performed by an implantable device including aprocessor, such as implantable device 104. In some embodiments of method900, implantable device 104 employs ID communication component 402, IDconnectivity monitoring component 404, ID connectivity assessmentcomponent 406 and/or ID notification component 408. Repetitivedescription of like elements employed in other embodiments describedherein is omitted for sake of brevity.

At 902, an implantable device including a processor (e.g., implantabledevice 104) transmits advertisement signals to an external device inassociation with initiating telemetry sessions with the external device.At 904, the implantable device monitors advertisement signal informationidentifying an amount of the advertisement signals transmitted to theexternal device within a defined time period. The implantable devicealso monitors telemetry session information identifying an amount of thetelemetry sessions established between the external device and theimplantable device within the defined time period. At 906, theimplantable device determines a ratio corresponding to the amount oftelemetry sessions established between the external device and theimplantable device within the defined time period relative to the amountof the advertisement signals transmitted to the external device withinthe defined time period. At 908, the device determines whether atelemetry connectivity problem exists between the external device andthe implantable device based on at least one of comparison of the ratiowith a threshold ratio or comparison of a number of discovery eventswithin the defined time period to a threshold number. For example, theimplantable device can determine that the telemetry connectivity problemexists based on the ratio being less than the threshold ratio. Inanother example, the implantable device can determine that the telemetryconnectivity problem exists based on the number of discovery eventsbeing below the threshold number.

FIG. 10 shows a flow diagram of another example method 1000 formonitoring integrity of telemetry connectivity between an implantabledevice and an external device in accordance with one embodiment. Variousembodiments of method 1000 can be performed by an implantable deviceincluding a processor, such as implantable device 104. In someembodiments of method 1000, implantable device 104 employs IDcommunication component 402 and/or ID configuration component 412.Repetitive description of like elements employed in other embodimentsdescribed herein is omitted for sake of brevity.

At 1002, an implantable device including a processor (e.g., implantabledevice 104), transmits advertisement signals to an external device inassociation with performing telemetry communication with the externaldevice using a defined telemetry communication protocol (e.g., a BLEbased communication protocol). At 1004, the implantable device receivesa command instructing the implantable device to reconfigure a parameterof the defined telemetry communication protocol based on a determination(e.g., made via ED connectivity assessment component 206 or SDconnectivity assessment component 606) that an amount of the advertisingsignals received by the external device from the implantable devicewithin the defined time period is below a threshold amount. At 1006, theimplantable device reconfigures the parameter of the defined telemetrycommunication protocol based on the command

FIG. 11 shows a flow diagram of another example method 1100 formonitoring integrity of telemetry connectivity between an implantabledevice and an external device in accordance with one embodiment. Variousembodiments of method 1100 can be performed by a device including aprocessor, such as server device 122. In some embodiments of method1100, server device 122 employs SD communication component 602, and SDconfiguration component 610. Repetitive description of like elementsemployed in other embodiments described herein is omitted for sake ofbrevity.

At 1102, a device including a processor (e.g., server device 122),receives telemetry connectivity information associated with telemetrycommunication between an implantable device (e.g., implantable device104) and an external device (e.g., external device 116). The telemetryconnectivity information includes at least one of: a number ofadvertisement signals sent by the implantable device to the externaldevice within a defined time period, an amount of the advertisementsignals that were received by the external device within the definedtime period or a number of successful telemetry sessions establishedbetween the implantable device and the external device within thedefined time period. At 1104, the device determines whether a telemetryconnectivity error condition associated with the telemetry communicationbetween the implantable device and the external device exists based onanalysis of the telemetry connectivity information. For example, thedevice can determine that a telemetry connectivity error conditionexists based on a miscorrelation between the number of advertisementsignals sent by the implantable device to the external device within adefined time period, the amount of the advertisement signals that werereceived by the external device within the defined time period, and/orthe number of successful telemetry sessions established between theimplantable device and the external device within the defined timeperiod. At 1106, the device generates a notification base on adetermination that the telemetry connectivity error condition exists.The notification can include information identifying the telemetryconnectivity error condition. At 1108, the device sends the notificationto the external device or another device.

FIG. 12 illustrates a block diagram of a computer operable to facilitatecommunication between an implantable device and an external device inaccordance with one or more embodiments described herein. For example,in some embodiments, the computer can be or be included withinimplantable device 104 and/or external device 116. Repetitivedescription of like elements employed in other embodiments describedherein is omitted for sake of brevity. Including, but not limited to,provide additional context for one or more embodiments described herein,FIG. 12 and the following discussion are intended to provide a brief,general description of a suitable computing environment 1200 in whichthe one or more embodiments described herein can be implemented.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structured dataor unstructured data. Tangible and/or non-transitory computer-readablestorage media can include, but are not limited to, random access memory(RAM), read only memory (ROM), electrically erasable programmable readonly memory (EEPROM), flash memory or other memory technology, compactdisk read only memory (CD-ROM), digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage, other magnetic storage devices and/or other media that can beused to store desired information. Computer-readable storage media canbe accessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium.

In this regard, the term “tangible” herein as applied to storage,memory, computer-readable media or computer-readable storage media, isto be understood to exclude only propagating intangible signals per seas a modifier and does not relinquish coverage of all standard storage,memory, computer-readable media or computer-readable storage media thatare not only propagating intangible signals per se.

In this regard, the term “non-transitory” herein as applied to storage,memory, computer-readable media or computer-readable storage media, isto be understood to exclude only propagating transitory signals per seas a modifier and does not relinquish coverage of all standard storage,memory, computer-readable media or computer-readable storage media thatare not only propagating transitory signals per se.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a channelwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of the data signal's characteristicsset or changed in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediainclude wired media, such as a wired network or direct-wired connection,and wireless media such as acoustic, RF, infrared and other wirelessmedia.

With reference again to FIG. 12, example environment 1200 that can beemployed to implement one or more embodiments of the embodimentsdescribed herein includes computer 1202. Computer 1202 includesprocessing unit 1204, system memory 1206 and system bus 1208. System bus1208 couples system components including, but not limited to, systemmemory 1206 to processing unit 1204. Processing unit 1204 can be any ofvarious commercially available processors. Dual microprocessors andother multi-processor architectures can also be employed as processingunit 1204.

System bus 1208 can be any of several types of bus structure that canfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. System memory 1206 includesRAM 1210 and ROM 1212. A basic input/output system (BIOS) can be storedin a non-volatile memory such as ROM, erasable programmable read onlymemory (EPROM), EEPROM, which BIOS contains the basic routines that helpto transfer information between elements within computer 1202, such asduring startup. RAM 1210 can also include a high-speed RAM such asstatic RAM for caching data.

Computer 1202 further includes internal hard disk drive (HDD) 1214(e.g., Enhanced Integrated Drive Electronics (EIDE), Serial AdvancedTechnology Attachment (SATA)). HDD 1214 can be connected to system bus1208 by hard disk drive interface 1216. The drives and their associatedcomputer-readable storage media provide nonvolatile storage of data,data structures, computer-executable instructions, and so forth. Forcomputer 1202, the drives and storage media accommodate the storage ofany data in a suitable digital format.

A number of program modules can be stored in the drives and RAM 1210,including operating system 1236, one or more application programs 1238,other program modules 1240 and program data 1242. All or portions of theoperating system, applications, modules, and/or data can also be cachedin RAM 1210. The systems and methods described herein can be implementedutilizing various commercially available operating systems orcombinations of operating systems.

A mobile device can enter commands and information into computer 1202through one or more wireless input devices, e.g., wireless keyboard 1228and a pointing device, such as wireless mouse 1230. Other input devices(not shown) can include a smart phone, tablet, laptop, wand, wearabledevice or the like. These and other input devices are often connected tothe processing unit 1204 through input device interface 1218 that can becoupled to system bus 1208, but can be connected by other interfaces,such as a parallel port, an IEEE serial port, a game port and/or auniversal serial bus (USB) port.

Computer 1202 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as remote computer(s) 1232. Remote computer(s)1232 can be a workstation, a server computer, a router, a personalcomputer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to computer1202, although, for purposes of brevity, only memory/storage device 1234is illustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 1226 and/or larger networks,e.g., WAN 1224, as well as smaller PANs involving a few devices (e.g.,at least two). LAN and WAN networking environments are commonplace inthe home, offices (e.g., medical facility offices, hospital offices) andcompanies, and facilitate enterprise-wide computer networks, such asintranets, all of which can connect to a global communications network(e.g., the Internet).

When used in a LAN networking environment, computer 1202 can beconnected to local network through a wired and/or wireless communicationnetwork interface or adapter 1220. Adapter 1220 can facilitate wired orwireless communication to LAN 1226, which can also include a wirelessaccess point (AP) connected to the LAN 1226 for communicating withadapter 1220.

When used in a WAN networking environment, computer 1202 can includemodem 1222 or can be connected to a communications server on WAN 1224 orhas other means for establishing communications over WAN 1224, such asby way of the Internet. Modem 1222, which can be internal or externaland a wired or wireless device, can be connected to system bus 1208 viainput device interface 1218. In a networked environment, program modulesdepicted relative to computer 1202 or portions thereof, can be stored ina remote memory/storage device. It will be appreciated that the networkconnections shown are example and other means of establishing acommunications link between the computers can be used.

Computer 1202 can be operable to communicate with any wireless devicesor entities operatively disposed in wireless communication via anynumber of protocols, including, but not limited to, NFC, Wi-Fi and/orBLUETOOTH® wireless protocols. Thus, the communication can be a definedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

NFC can allow point-to-point connection to an NFC-enabled device in theNFC field of an IMD within the home or at any location. NFC technologycan be facilitated using an NFC-enabled smart phone, tablet or otherdevice that can be brought within 3-4 centimeters of an implanted NFCcomponent. NFC typically provides a maximum data rate of 424 kilobitsper second (Kbps), although data rates can range from 6.67 Kbps to 828Kbps. NFC typically operates at the frequency of 13.56 megahertz (MHz).NFC technology communication is typically over a range not exceeding 0.2meters (m) and setup time can be less than 0.1 seconds. Low power (e.g.,12 milliamperes (mAs)) reading of data can be performed by an NFCdevice.

Wi-Fi can allow connection to the Internet from a couch at home, a bedin a hotel room or a conference room at work, without wires. Wi-Fi is awireless technology similar to that used in a cell phone that enablessuch devices, e.g., computers, to send and receive data indoors and out.Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n,etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Finetwork can be used to connect computers to each other, to the Internet,and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

The embodiments of devices described herein can employ artificialintelligence (AI) to facilitate automating one or more featuresdescribed herein. The embodiments (e.g., in connection withautomatically identifying acquired cell sites that provide a maximumvalue/benefit after addition to an existing communication network) canemploy various AI-based schemes for carrying out one or more embodimentsthereof. Moreover, the classifier can be employed to determine a rankingor priority of each cell site of an acquired network. A classifier is afunction that maps an input attribute vector, x=(x1, x2, x3, x4, xn), toa confidence that the input belongs to a class, that is,f(x)=confidence(class). Such classification can employ a probabilisticand/or statistical-based analysis (e.g., factoring into the analysisutilities and costs) to prognose or infer an action that a mobile devicedesires to be automatically performed. A support vector machine (SVM) isan example of a classifier that can be employed. The SVM operates byfinding a hypersurface in the space of possible inputs, which thehypersurface attempts to split the triggering criteria from thenon-triggering events. Intuitively, this makes the classificationcorrect for testing data that is near, but not identical to trainingdata. Other directed and undirected model classification approachesinclude, e.g., naïve Bayes, Bayesian networks, decision trees, neuralnetworks, fuzzy logic models, and probabilistic classification modelsproviding different patterns of independence can be employed.Classification as used herein also is inclusive of statisticalregression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments canemploy classifiers that are explicitly trained (e.g., via a generictraining data) as well as implicitly trained (e.g., via observing mobiledevice behavior, operator preferences, historical information, receivingextrinsic information). For example, SVMs can be configured via alearning or training phase within a classifier constructor and featureselection module. Thus, the classifier(s) can be used to automaticallylearn and perform a number of functions, including but not limited todetermining according to a defined criteria which of the acquired cellsites will benefit a maximum number of subscribers and/or which of theacquired cell sites will add minimum value to the existing communicationnetwork coverage, etc.

As employed herein, the term “processor” can refer to substantially anycomputing processing unit or device including, but not limited to,single-core processors; single-processors with software multithreadexecution capability; multi-core processors; multi-core processors withsoftware multithread execution capability; multi-core processors withhardware multithread technology; parallel platforms; and parallelplatforms with distributed shared memory. Additionally, a processor canrefer to an integrated circuit, an application specific integratedcircuit (ASIC), a digital signal processor (DSP), a field programmablegate array (FPGA), a programmable logic controller (PLC), a complexprogrammable logic device (CPLD), a discrete gate or transistor logic,discrete hardware components or any combination thereof designed toperform the functions described herein. Processors can exploitnano-scale architectures such as, but not limited to, molecular andquantum-dot based transistors, switches and gates, including, but notlimited to, optimize space usage or enhance performance of mobile deviceequipment. A processor can also be implemented as a combination ofcomputing processing units.

Memory disclosed herein can include volatile memory or nonvolatilememory or can include both volatile and nonvolatile memory. By way ofillustration, and not limitation, nonvolatile memory can include ROM,programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable PROM (EEPROM) or flash memory. Volatile memory caninclude RAM, which acts as external cache memory. By way of illustrationand not limitation, RAM is available in many forms such as static RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). The memory (e.g., data storages, databases)of the embodiments is intended to include, without being limited to,these and any other suitable types of memory.

As used herein, terms such as “data storage,” “database,” andsubstantially any other information storage component relevant tooperation and functionality of a component, refer to “memorycomponents,” or entities embodied in a “memory” or components includingthe memory. It will be appreciated that the memory components orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory or can include both volatile andnonvolatile memory.

In addition, the words “example” and “exemplary” are used herein to meanserving as an instance or illustration. Any embodiment or designdescribed herein as “example” or “exemplary” is not necessarily to beconstrued as preferred or advantageous over other embodiments ordesigns. Rather, use of the word “example” or “exemplary” is intended topresent concepts in a concrete fashion. As used in this application, theterm “or” is intended to mean an inclusive “or” rather than an exclusive“or”. That is, unless specified otherwise or clear from context, “Xemploys A or B” is intended to mean any of the natural inclusivepermutations. That is, if X employs A; X employs B; or X employs both Aand B, then “X employs A or B” is satisfied under any of the foregoinginstances. In addition, the articles “a” and “an” as used in thisapplication should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform. The terms “first,” “second,” “third,” and so forth, as used in theclaims and description, unless otherwise clear by context, is forclarity only and doesn't necessarily indicate or imply any order intime.

What has been described above includes mere examples of one or moreembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing these examples, but one of ordinary skill in the art canrecognize that many further combinations and permutations of the presentembodiments are possible. Accordingly, the embodiments disclosed and/orclaimed herein are intended to embrace all such alterations,modifications and variations that fall within the spirit and scope ofthe detailed description and the appended claims. Furthermore, to theextent that the term “includes” is used in either the detaileddescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. An implantable device, comprising: a memory thatstores executable components; and a processor that executes theexecutable components stored in the memory, wherein the executablecomponents comprise: a monitoring component configured to monitoradvertisement signal information identifying an amount of advertisementsignals transmitted from the implantable device to an external devicewithin a defined time period, and telemetry session informationidentifying an amount of telemetry sessions that are established betweenthe external device and the implantable device within the defined timeperiod; and a connectivity assessment component configured to determinewhether a telemetry connectivity problem exists between the externaldevice and the implantable device based on at least one of a number ofdiscovery events within the defined time period or a ratio correspondingto the amount of telemetry sessions that are established between theexternal device and the implantable device within the defined timeperiod relative to the amount of the advertisement signals transmittedto the external device within the defined time period.
 2. Theimplantable device of claim 1, wherein the connectivity assessmentcomponent is configured to determine that the telemetry connectivityproblem exists between the external device and the implantable devicebased on at least one of the number of discovery events being less thana threshold number or the ratio being less than a threshold ratio. 3.The implantable device of claim 2, further comprising: a notificationcomponent configured to generate a notification indicating the telemetryconnectivity problem exists between the external device and theimplantable device based on a determination that at least one of thenumber of discovery events is below the threshold number or the ratio isbelow the threshold ratio, and wherein the notification component isfurther configured to send the notification to the external device forat least one of rendering at the external device or relaying, by theexternal device, to another device.
 4. The implantable device of claim1, further comprising: a reporting component configured to send theadvertisement signal information to the external device.
 5. Theimplantable device of claim 1, further comprising: a configurationcomponent configured to receive a command instructing the implantabledevice to reconfigure a telemetry communication protocol employed by theimplantable device to communicate with the external device based on adetermination that an amount of the advertisement signals that arereceived by the external device from the implantable device within thedefined time period is below a threshold amount.
 6. The implantabledevice of claim 5, wherein the configuration component is configured toreceive the command from the external device and wherein the commandoriginated from a server device that is separate from the externaldevice.
 7. The implantable device of claim 1, wherein the monitoringcomponent is further configured to monitor interrogation signalinformation identifying an amount of interrogation signals received fromthe external device within the defined time period, and wherein theconnectivity assessment component is further configured to determinethat the telemetry connectivity problem exists between the externaldevice and the implantable device based on the amount of interrogationsignals received being below a threshold amount.
 8. The implantabledevice of claim 1, wherein the monitoring component is furtherconfigured to monitor interrogation signal information identifying anamount of interrogation signals received from the external device withinthe defined time period, and wherein the connectivity assessmentcomponent is further configured to determine that the telemetryconnectivity problem exists between the external device and theimplantable device based on a second ratio, corresponding to the amountof interrogation signals received within the defined time periodrelative to the amount of telemetry sessions established between theexternal device and the implantable device within the defined timeperiod, being less than a threshold ratio.
 9. The implantable device ofclaim 1, wherein the monitoring component is further configured tomonitor signal strength information identifying strengths of signalsreceived from the external device within the defined time period, andwherein the connectivity assessment component is further configured todetermine that the telemetry connectivity problem exists between theexternal device and the implantable device based on an average strengthof the strengths of the signals received being less than a thresholdamount.
 10. The implantable device of claim 1, wherein the monitoringcomponent is further configured to monitor signal strength informationidentifying strengths of signals received from the external devicewithin the defined time period, and wherein the connectivity assessmentcomponent is further configured to determine that the telemetryconnectivity problem exists between the external device and theimplantable device based on a degree of variance in the strengths of thesignals received exceeding a threshold degree of variance.
 11. Theimplantable device of claim 1, wherein the monitoring component isfurther configured to monitor throughput information identifyingthroughput of data packets received from the external device within thedefined time period, and wherein the connectivity assessment componentis further configured to determine that the telemetry connectivityproblem exists between the external device and the implantable devicebased on the throughput being less than a threshold amount.
 12. Theimplantable device of claim 1, wherein the monitoring component isfurther configured to monitor throughput information identifyingthroughput of data packets transmitted by the implantable device to theexternal device within the defined time period, and wherein theconnectivity assessment component is further configured to determinethat the telemetry connectivity problem exists between the externaldevice and the implantable device based on throughput being less than athreshold amount.
 13. The implantable device of claim 1, wherein theimplantable device further comprises a communication componentconfigured to transmit the advertisement signals to the external deviceusing a BLUETOOTH® Low Energy communication protocol.
 14. A method,comprising: monitoring, by a device comprising a processor, telemetryconnectivity information comprising advertisement signal informationidentifying times advertisement signals are received by the device froman implantable device; determining, by the device, whether a telemetryconnectivity error condition exists associated with performing telemetrycommunication between the device and the implantable device based on anamount of the advertisement signals received within a defined timeperiod relative to a threshold amount; and generating, by the device, anotification identifying the telemetry connectivity error conditionbased on a determination that the telemetry connectivity error conditionexists.
 15. The method of claim 14, wherein the determining comprisesdetermining that the telemetry connectivity error condition exists basedon the amount of the advertisement signals received within the definedtime period being below the threshold amount.
 16. The method of claim14, further comprising performing at least one of rendering, by thedevice, the notification at the device, or transmitting, by the device,the notification to another device, wherein the other device comprisesthe implantable device or a server device.
 17. The method of claim 14,wherein the determining further comprises determining that the telemetryconnectivity error condition exists based on a duration of time betweenreception of two or more of the advertisement signals being above athreshold duration.
 18. The method of claim 14, wherein the telemetryconnectivity information further comprises telemetry session informationidentifying an amount of telemetry sessions established between thedevice and the implantable device within the defined time period, andwherein the determining whether the telemetry connectivity errorcondition exists is also based on a percentage value corresponding tothe amount of telemetry sessions established relative to the amount ofthe advertisement signals received being less than a thresholdpercentage value.
 19. A device, comprising: a monitoring componentconfigured to monitor telemetry connectivity information comprisingadvertisement signal information identifying times at whichadvertisement signals, transmitted by an implantable device, arereceived by the device; a connectivity assessment component configuredto determine whether a telemetry connectivity error condition existsassociated with performance of telemetry communication with theimplantable device based on an amount of the advertisement signalsreceived within a defined time period relative to a threshold amount;and a notification component configured to generate a notificationidentifying the telemetry connectivity error condition based on adetermination that the telemetry connectivity error condition exists.20. The device of claim 19, wherein the connectivity assessmentcomponent is configured to determine that the telemetry connectivityerror condition exists based on the amount of the advertisement signalsreceived within the defined time period being below the thresholdamount.
 21. The device of claim 19, wherein the connectivity assessmentcomponent is configured to determine that the telemetry connectivityerror condition exists based on the amount of the advertisement signalsreceived within the defined time period being above one of the thresholdamount or another threshold amount.
 22. The device of claim 19, whereinthe notification component is further configured to render thenotification at the device.
 23. A system comprising: an implantabledevice configured to transmit advertisement signals using a definedtelemetry communication protocol; and an external device configured to:monitor advertisement signal information associated with theadvertisement signals; identify an amount of the advertisement signalsreceived by the external device within a defined period of time; andfacilitate determining whether a telemetry connectivity error conditionexists in association with performance of telemetry communication withthe implantable device based on an evaluation of the advertisementsignal information with respect to the defined telemetry communicationprotocol.
 24. The system of claim 23, wherein the external device isfurther configured to perform the evaluation based on a determinationthat the amount of the advertisement signals received is below athreshold amount.
 25. The system of claim 24, wherein the externaldevice is further configured to: generate a notification identifying thetelemetry connectivity error condition based on the determination; andat least one of render the notification at the external device or sendthe notification to at least one of the implantable device or anotherdevice.
 26. The system of claim 23, further comprising: a server devicecommunicatively coupled to the external device, wherein the externaldevice is configured to send the advertisement signal information to theserver device, and wherein the server device is configured to performthe evaluation of the advertisement signal information, includingdetermining that the telemetry connectivity error condition exists,based on a determination that the amount of the advertisement signalsreceived is below a threshold amount.
 27. The system of claim 26,wherein the server device is further configured to: generate anotification identifying the telemetry connectivity error conditionbased on the determination; and send the notification to another device,wherein the other device comprises at least one of the external device,the implantable device or another external device.